← previous blocknext block →recent activity
Analyzing
Block #86,766,973
19 transactions · 17 stateful · 2026-07-10 04:30:11 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,766,973 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w19w010w211w312w113w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x3e6563f1…1c23
0x34b655…2a6f
10 touches
10 conflicts
0xec7fe04a…3c56
0x34b655…2a6f
6 touches
3 conflicts
0x453f53a8…e541
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x1c03f81f…b303
0x34b655…2a6f
6 touches
3 conflicts
0x74550a4b…68bd
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x92385428ad…dc6941
Audit this contract →
← previous block·next block →recent activity