← previous blocknext block →recent activity
Analyzing
Block #86,915,976
17 transactions · 13 stateful · 2026-07-10 21:06:11 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,915,976 · 17 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
2w03w15w07w18w210w311w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x0229f70b…6dce
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0a0cecef…4ed0
0x34b655…2a6f
4 touches
1 conflict
0x0e1e4f92…4c29
0x34b655…2a6f
4 touches
1 conflict
0x1191dbf7…8e85
0x34b655…2a6f
4 touches
1 conflict
0x3034af96…e290
0x34b655…2a6f
4 touches
1 conflict
0xdf708ee7…1fcf
0xc8689a…ee79
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity