← previous blocknext block →recent activity
Analyzing
Block #112,484,587
30 transactions · 27 stateful · 2026-10-11 13:48:43 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #112,484,587 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w010w011w112w013w214w215w316w417w518w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d5bad6c…76cc
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0xdad20621…06b1
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0x062fc6c1…d642
0x34b655…2a6f
4 touches
1 conflict
0x137538b5…3e75
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 0x5d5bad6ca2…2676cc
Audit this contract →
← previous block·next block →recent activity