← previous blocknext block →recent activity
Analyzing
Block #86,987,816
27 transactions · 24 stateful · 2026-07-11 05:06:12 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,987,816 · 27 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
2w03w112w013w214w119w220w123w324w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a65207b…4f30
0x34b655…2a6f
6 touches
3 conflicts
0x5b37bb6b…aaff
0x34b655…2a6f
6 touches
3 conflicts
0x5b37bb6b…ab00
0x34b655…2a6f
6 touches
3 conflicts
0x66cc379b…36fd
0x34b655…2a6f
6 touches
3 conflicts
0xa1f3bb32…4544
0x34b655…2a6f
6 touches
3 conflicts
0xee4fe1f7…3ead
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x6f704795…17bc
0xd32edf…ff58
5 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
3 conflicts on slot 0x5a65207bfd…e54f30
Audit this contract →
← previous block·next block →recent activity