← previous blocknext block →recent activity
Analyzing
Block #86,273,372
16 transactions · 14 stateful · 2026-07-07 21:29:37 UTC
Parallelism
69/100
Blocked
57%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,273,372 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w08w110w211w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bd95eb4…e562
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0x4786b2fa…692f
0xd32edf…ff58
5 touches
3 conflicts
0x2697123c…8526
0x34b655…2a6f
4 touches
1 conflict
0x2ed98d3b…78ef
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0x379bef0d…1d85
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 0x0bd95eb406…f6e562
Audit this contract →
← previous block·next block →recent activity