← previous blocknext block →recent activity
Analyzing
Block #86,923,016
12 transactions · 9 stateful · 2026-07-10 21:53:14 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,923,016 · 12 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
1w02w13w25w17w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x2cebbc04…8b01
0x34b655…2a6f
4 touches
1 conflict
0x3d248e74…b607
0x34b655…2a6f
4 touches
1 conflict
0x472dd61b…64fe
0x34b655…2a6f
4 touches
1 conflict
0x5144c81e…a39e
0x34b655…2a6f
4 touches
1 conflict
0x5379f516…8bf2
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity