← previous blocknext block →recent activity
Analyzing
Block #86,823,989
16 transactions · 16 stateful · 2026-07-10 10:51:12 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,823,989 · 16 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
4w05w17w28w39w414w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55625899…9074
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xaba6578d…bd48
0x34b655…2a6f
6 touches
3 conflicts
0xded7831c…3c4a
0x34b655…2a6f
6 touches
3 conflicts
0xab4a9e70…a605
0x34b655…2a6f
6 touches
3 conflicts
0x7eab4979…0d6c
0x34b655…2a6f
6 touches
3 conflicts
0xaa431b7f…9ebf
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 0x55625899ba…5b9074
Audit this contract →
← previous block·next block →recent activity