← previous blocknext block →recent activity
Analyzing
Block #112,588,749
16 transactions · 13 stateful · 2026-10-11 22:32:47 UTC
Parallelism
69/100
Blocked
54%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,588,749 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w19w110w211w312w413w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e1329b8…deca
0x34b655…2a6f
8 touches
6 conflicts
0x7df607f5…a36d
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0x5274371f…a348
0x1b6862…e19c
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 0x3e1329b8d3…2fdeca
Audit this contract →
← previous block·next block →recent activity