← previous blocknext block →recent activity
Analyzing
Block #86,658,741
23 transactions · 15 stateful · 2026-07-09 16:27:27 UTC
Parallelism
78/100
Blocked
60%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,658,741 · 23 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
1w02w13w24w35w07w19w010w211w112w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c04ce68…d007
0x34b655…2a6f
6 touches
3 conflicts
0xe5a38e46…a68c
0x34b655…2a6f
6 touches
3 conflicts
0x9e3cc051…a058
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xdb95e18e…c737
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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
3 conflicts on slot 0x4c04ce6804…bbd007
Audit this contract →
← previous block·next block →recent activity