← previous blocknext block →recent activity
Analyzing
Block #86,964,781
12 transactions · 12 stateful · 2026-07-11 02:32:20 UTC
Parallelism
58/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,964,781 · 12 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
2w05w16w27w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb652c396…b8fa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xe5acefce…a322
0x34b655…2a6f
4 touches
1 conflict
0xa9988419…9f45
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
0x34b655…2a6f
2 touches
0 conflicts
0x9c540cb6…ea0c
0x34b655…2a6f
2 touches
0 conflicts
0xcd81cc7b…8da0
0x34b655…2a6f
2 touches
0 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 0xb652c39667…34b8fa
Audit this contract →
← previous block·next block →recent activity