← previous blocknext block →recent activity
Analyzing
Block #86,315,698
13 transactions · 9 stateful · 2026-07-08 02:12:14 UTC
Parallelism
77/100
Blocked
22%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,315,698 · 13 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
1w02w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f6aef87…8137
0x34b655…2a6f
4 touches
1 conflict
0x3bdd71a2…b6eb
0x34b655…2a6f
4 touches
1 conflict
0x9dd0a735…4d04
0x34b655…2a6f
4 touches
1 conflict
0x0ec9e741…0f70
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
2 touches
0 conflicts
0x404314de…df1a
0x3bd359…433a
2 touches
0 conflicts
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0xb98b9e9d…a785
0x3bd359…433a
2 touches
0 conflicts
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
1 conflict on slot 0x0f6aef8771…dd8137
Audit this contract →
← previous block·next block →recent activity