← previous blocknext block →recent activity
Analyzing
Block #86,664,229
25 transactions · 25 stateful · 2026-07-09 17:04:03 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,664,229 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w07w19w010w115w016w117w218w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…000a
0x90c374…be45
8 touches
6 conflicts
0x00000000…000b
0x90c374…be45
8 touches
6 conflicts
0x34443913…cbf3
0x336ed4…c59c
6 touches
3 conflicts
0x50c0dd87…1128
0x34b655…2a6f
4 touches
1 conflict
0x6b3a2279…1115
0x34b655…2a6f
4 touches
1 conflict
0x9dd0a735…4d04
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
10 conflicts on slot 0x92385428ad…dc6941
Audit this contract →
← previous block·next block →recent activity