← previous blocknext block →recent activity
Analyzing
Block #86,057,677
20 transactions · 20 stateful · 2026-07-06 21:29:45 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,057,677 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w28w010w111w112w315w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6d040d9…9ae3
0x34b655…2a6f
6 touches
3 conflicts
0x76ed8777…1e5f
0x34b655…2a6f
6 touches
3 conflicts
0xe6e6f436…ddc0
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x204ccae2…8dc1
0x34b655…2a6f
4 touches
1 conflict
0x3d158563…8713
0x34b655…2a6f
4 touches
1 conflict
0x40b8f0ac…20bb
0x34b655…2a6f
4 touches
1 conflict
0x756913cf…e7bd
0xa6afd3…d132
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 0xd6d040d989…9c9ae3
Audit this contract →
← previous block·next block →recent activity