← previous blocknext block →recent activity
Analyzing
Block #112,336,319
14 transactions · 14 stateful · 2026-10-11 01:22:45 UTC
Parallelism
71/100
Blocked
21%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,336,319 · 14 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
2w03w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7aad02c6…b979
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xd8936bb8…e417
0xf42df8…ad97
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x5f801a91…6a09
0x34b655…2a6f
4 touches
1 conflict
0x796dc7ca…574a
0x34b655…2a6f
4 touches
1 conflict
0x7bbe2359…c036
0x34b655…2a6f
4 touches
1 conflict
0xb9f1f9af…4c13
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 0x7aad02c682…feb979
Audit this contract →
← previous block·next block →recent activity