← previous blocknext block →recent activity
Analyzing
Block #86,681,301
23 transactions · 21 stateful · 2026-07-09 18:58:01 UTC
Parallelism
74/100
Blocked
48%
Avg conflicts / tx
0.91
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,681,301 · 23 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
2w03w04w15w26w39w010w111w112w214w316w421w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1af19f5c…aee2
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x5fee1ba0…2520
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x727fbce7…0c80
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
6 conflicts on slot 0x1af19f5c41…14aee2
Audit this contract →
← previous block·next block →recent activity