← previous blocknext block →recent activity
Analyzing
Block #112,611,864
22 transactions · 18 stateful · 2026-10-12 00:29:05 UTC
Parallelism
86/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #112,611,864 · 22 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
1w04w05w111w015w118w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef218c67…caf4
0x34b655…2a6f
4 touches
1 conflict
0x042a5cf5…a3d6
0x34b655…2a6f
4 touches
1 conflict
0x1e737223…2278
0x34b655…2a6f
4 touches
1 conflict
0xb473d944…85a5
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd71173c4…c3a4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe6fda39e…53c9
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
1 conflict on slot 0xef218c678e…74caf4
Audit this contract →
← previous block·next block →recent activity