← previous blocknext block →recent activity
Analyzing
Block #86,319,461
18 transactions · 16 stateful · 2026-07-08 02:37:24 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,319,461 · 18 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
2w03w04w15w26w09w110w011w116w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca2926e0…61b5
0x34b655…2a6f
8 touches
6 conflicts
0xaa1dd7d8…b929
0x34b655…2a6f
8 touches
6 conflicts
0x99701186…1cbf
0x34b655…2a6f
6 touches
3 conflicts
0x4bfdcd51…9b58
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0x034f1f86…4e8d
0x34b655…2a6f
6 touches
3 conflicts
0x6db97e95…8353
0x34b655…2a6f
4 touches
1 conflict
0x98b22a44…2d63
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 0xca2926e0af…1961b5
Audit this contract →
← previous block·next block →recent activity