← previous blocknext block →recent activity
Analyzing
Block #112,255,340
13 transactions · 11 stateful · 2026-10-10 18:35:20 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #112,255,340 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w110w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x8c211514…b757
0x34b655…2a6f
4 touches
1 conflict
0xabdd2e65…212a
0x34b655…2a6f
4 touches
1 conflict
0xb4656137…5858
0x34b655…2a6f
4 touches
1 conflict
0xc4550172…3d03
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x2ab97ba4…f5a8
0x34b655…2a6f
4 touches
1 conflict
0xfd8a372a…4f6b
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity