← previous blocknext block →recent activity
Analyzing
Block #86,767,971
21 transactions · 18 stateful · 2026-07-10 04:36:52 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,767,971 · 21 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
1w02w13w24w05w16w07w18w211w312w413w114w515w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb0b1d43…9559
0x34b655…2a6f
8 touches
6 conflicts
0xd216df1a…c818
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xac3e4969…39e9
0x34b655…2a6f
6 touches
3 conflicts
0x15fd0ad9…ce63
0xd32edf…ff58
5 touches
3 conflicts
0x581b829b…9578
0x34b655…2a6f
4 touches
1 conflict
0xd0ec9500…6194
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 0xeb0b1d4366…fc9559
Audit this contract →
← previous block·next block →recent activity