← previous blocknext block →recent activity
Analyzing
Block #86,707,792
21 transactions · 20 stateful · 2026-07-09 21:54:44 UTC
Parallelism
71/100
Blocked
30%
Avg conflicts / tx
0.48
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,707,792 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w17w28w012w315w016w118w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bd95eb4…e562
0x34b655…2a6f
6 touches
3 conflicts
0x3347cbe5…846c
0x34b655…2a6f
6 touches
3 conflicts
0x67a9f76d…0b84
0x34b655…2a6f
6 touches
3 conflicts
0x9c7d2e4b…499b
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xa771fb55…48d2
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
3 conflicts on slot 0x0bd95eb406…f6e562
Audit this contract →
← previous block·next block →recent activity