← previous blocknext block →recent activity
Analyzing
Block #86,491,194
30 transactions · 23 stateful · 2026-07-08 21:45:02 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,491,194 · 30 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
1w03w04w16w08w19w114w015w116w217w318w419w020w121w025w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x3230277c…ef39
0xc8689a…ee79
6 touches
3 conflicts
0x68e52406…3352
0x34b655…2a6f
6 touches
3 conflicts
0x452f2538…1cfc
0x34b655…2a6f
6 touches
3 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
6 touches
3 conflicts
0xd911522b…e960
0x34b655…2a6f
6 touches
3 conflicts
0xdba422af…42ec
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity