← previous blocknext block →recent activity
Analyzing
Block #112,236,508
30 transactions · 21 stateful · 2026-10-10 17:00:35 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,236,508 · 30 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
1w012w013w014w115w020w122w223w326w327w428w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc4550172…3d03
0x34b655…2a6f
6 touches
3 conflicts
0x83b5b358…ec06
0x34b655…2a6f
6 touches
3 conflicts
0x9195dd67…6489
0x34b655…2a6f
4 touches
1 conflict
0x931975c2…b7b3
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb0f5d668…99ac
0x34b655…2a6f
4 touches
1 conflict
0xb40e601f…bf98
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity