← previous blocknext block →recent activity
Analyzing
Block #86,904,384
14 transactions · 10 stateful · 2026-07-10 19:48:43 UTC
Parallelism
64/100
Blocked
60%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,904,384 · 14 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
1w02w13w25w06w37w411w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7da56943…9753
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0xbde30d77…b032
0x34b655…2a6f
6 touches
3 conflicts
0xd064a456…b881
0x34b655…2a6f
6 touches
3 conflicts
0xe68ed94b…3662
0x34b655…2a6f
6 touches
3 conflicts
0xe6d4c76c…2179
0x34b655…2a6f
6 touches
3 conflicts
0xedcf2991…8551
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 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 0x7da56943bc…d89753
Audit this contract →
← previous block·next block →recent activity