← previous blocknext block →recent activity
Analyzing
Block #86,679,748
16 transactions · 14 stateful · 2026-07-09 18:47:37 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,679,748 · 16 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
3w04w15w06w17w29w310w411w514w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b374c44…96d9
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xf23e15be…1749
0x34b655…2a6f
6 touches
3 conflicts
0xe5a1a5cb…5ca1
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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
6 conflicts on slot 0x1b374c447e…d896d9
Audit this contract →
← previous block·next block →recent activity