← previous blocknext block →recent activity
Analyzing
Block #86,789,719
19 transactions · 15 stateful · 2026-07-10 07:01:58 UTC
Parallelism
68/100
Blocked
33%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,789,719 · 19 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
4w06w17w28w39w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1a8
0xb1dbf0…c0d3
7 touches
6 conflicts
0x0178c2de…b37d
0xb1dbf0…c0d3
6 touches
3 conflicts
0x74825c4e…32e9
0xb1dbf0…c0d3
6 touches
3 conflicts
0x6d99ac64…0aa3
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0004
0xb1dbf0…c0d3
6 touches
3 conflicts
0x9cddb1b1…c504
0x34b655…2a6f
4 touches
1 conflict
0xa6b873a5…cffb
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity