← previous blocknext block →recent activity
Analyzing
Block #86,773,663
21 transactions · 17 stateful · 2026-07-10 05:14:54 UTC
Parallelism
48/100
Blocked
59%
Avg conflicts / tx
1.9
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #86,773,663 · 21 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w617w719w920w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7fe04a…3c56
0x34b655…2a6f
16 touches
28 conflicts
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
12 touches
15 conflicts
0x4a370d8b…2f60
0x34b655…2a6f
12 touches
15 conflicts
0x4e782273…1690
0x34b655…2a6f
12 touches
15 conflicts
0x56cb65af…855b
0x34b655…2a6f
12 touches
15 conflicts
0x64a785e4…0110
0x34b655…2a6f
12 touches
15 conflicts
0x7d1102d9…9f17
0x34b655…2a6f
12 touches
15 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
28 conflicts on slot 0xec7fe04ad1…2d3c56
Audit this contract →
← previous block·next block →recent activity