← previous blocknext block →recent activity
Analyzing
Block #112,580,721
17 transactions · 11 stateful · 2026-10-11 21:52:24 UTC
Parallelism
88/100
Blocked
9%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,580,721 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
10w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3321cb6…26de
0x34b655…2a6f
4 touches
1 conflict
0xa171740d…8340
0x34b655…2a6f
4 touches
1 conflict
0x6df1d50f…8a92
0x34b655…2a6f
4 touches
1 conflict
0x974f4f00…226d
0x34b655…2a6f
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
0x68c07cb9…ae14
0x34b655…2a6f
2 touches
0 conflicts
0x8b76e9f2…54ee
0x34b655…2a6f
2 touches
0 conflicts
0x9ae859db…2d84
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
1 conflict on slot 0xe3321cb684…3926de
Audit this contract →
← previous block·next block →recent activity