← previous blocknext block →recent activity
Analyzing
Block #112,492,688
16 transactions · 13 stateful · 2026-10-11 14:29:28 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #112,492,688 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w09w010w111w212w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe7987f14…5b90
0x34b655…2a6f
4 touches
1 conflict
0x26a0aeb6…2905
0x34b655…2a6f
4 touches
1 conflict
0x2a8be7d3…8ccb
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x55765606…9e50
0x34b655…2a6f
4 touches
1 conflict
0x818b417e…d299
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 0xe720a4c698…508eb0
Audit this contract →
← previous block·next block →recent activity