← previous blocknext block →recent activity
Analyzing
Block #86,829,915
24 transactions · 21 stateful · 2026-07-10 11:30:48 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,829,915 · 24 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
1w02w15w06w19w110w111w216w020w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25e0daa5…d833
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x2f2d2f35…bd40
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x59b0a8da…0928
0x34b655…2a6f
4 touches
1 conflict
0x6b2ba712…0214
0x34b655…2a6f
4 touches
1 conflict
0x79ace5b6…8d37
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 0x25e0daa5d1…b7d833
Audit this contract →
← previous block·next block →recent activity