← previous blocknext block →recent activity
Analyzing
Block #112,418,617
11 transactions · 11 stateful · 2026-10-11 08:16:47 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,418,617 · 11 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
2w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x336486a4…20bd
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xc2128da8…3551
0x34b655…2a6f
4 touches
1 conflict
0x68055fa2…229e
0x34b655…2a6f
2 touches
0 conflicts
0xa60a846b…cb55
0x34b655…2a6f
2 touches
0 conflicts
0xc6b75e8a…fae8
0x34b655…2a6f
2 touches
0 conflicts
0xc7c000b3…9346
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity