← previous blocknext block →recent activity
Analyzing
Block #112,486,286
13 transactions · 13 stateful · 2026-10-11 13:57:16 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,486,286 · 13 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
2w04w15w07w08w19w210w311w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51af0e92…4020
0x34b655…2a6f
8 touches
6 conflicts
0x78c07cee…a93d
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x054c8b6d…645a
0x34b655…2a6f
4 touches
1 conflict
0x00b872aa…2957
0x34b655…2a6f
4 touches
1 conflict
0x107b89e4…470d
0x34b655…2a6f
4 touches
1 conflict
0x3732c6c9…ded6
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 0x51af0e92a5…be4020
Audit this contract →
← previous block·next block →recent activity