← previous blocknext block →recent activity
Analyzing
Block #112,485,897
20 transactions · 16 stateful · 2026-10-11 13:55:18 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,485,897 · 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
4w05w112w013w115w216w317w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0af787a5…4ecc
0x34b655…2a6f
6 touches
3 conflicts
0xbccc364c…6842
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x125f12…a50b
4 touches
1 conflict
0x089d3365…d531
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x43eb6354…37d7
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
3 conflicts on slot 0x0af787a52c…2a4ecc
Audit this contract →
← previous block·next block →recent activity