← previous blocknext block →recent activity
Analyzing
Block #112,557,381
13 transactions · 11 stateful · 2026-10-11 19:54:59 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,557,381 · 13 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x266dbf0e…39fd
0x34b655…2a6f
4 touches
1 conflict
0x7bd229ad…63b2
0x34b655…2a6f
4 touches
1 conflict
0xaa3cf307…30e8
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0x190b178a…c154
0x34b655…2a6f
2 touches
0 conflicts
0x368499cd…c229
0x34b655…2a6f
2 touches
0 conflicts
0x4a4c0b59…93d5
0x34b655…2a6f
2 touches
0 conflicts
0x9bca659b…d468
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 0x266dbf0e79…2c39fd
Audit this contract →
← previous block·next block →recent activity