← previous blocknext block →recent activity
Analyzing
Block #111,810,553
10 transactions · 9 stateful · 2026-10-09 05:17:24 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #111,810,553 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w18w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x24dc9eeb…1126
0x34b655…2a6f
4 touches
1 conflict
0xfcec3ed3…26a9
0x34b655…2a6f
4 touches
1 conflict
0x0ec07cf7…c0c9
0x34b655…2a6f
2 touches
0 conflicts
0x1159bcfb…a105
0x34b655…2a6f
2 touches
0 conflicts
0x12f81d84…c430
0x34b655…2a6f
2 touches
0 conflicts
0x2b612c9a…6c77
0x34b655…2a6f
2 touches
0 conflicts
0x36951b5a…d5be
0x34b655…2a6f
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity