← previous blocknext block →recent activity
Analyzing
Block #112,483,424
20 transactions · 19 stateful · 2026-10-11 13:42:52 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,483,424 · 20 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
2w06w17w28w311w012w116w017w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7d9ef283…ddd1
0x34b655…2a6f
8 touches
6 conflicts
0x8013fa1b…b030
0x34b655…2a6f
4 touches
1 conflict
0x8b94749e…d466
0x34b655…2a6f
4 touches
1 conflict
0xa000657b…a094
0x34b655…2a6f
4 touches
1 conflict
0x0008ef72…a804
0x34b655…2a6f
4 touches
1 conflict
0x1972739d…a40b
0x34b655…2a6f
4 touches
1 conflict
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity