← previous blocknext block →recent activity
Analyzing
Block #86,711,943
19 transactions · 16 stateful · 2026-07-09 22:22:25 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.68
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,711,943 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w410w011w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x813d6148…7e8f
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
8 touches
6 conflicts
0x5a310d83…cae0
0x34b655…2a6f
6 touches
3 conflicts
0x64a785e4…0110
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity