← previous blocknext block →recent activity
Analyzing
Block #86,445,774
29 transactions · 21 stateful · 2026-07-08 16:41:10 UTC
Parallelism
86/100
Blocked
52%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,445,774 · 29 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
1w02w03w14w15w211w012w113w217w018w119w320w321w226w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x9fb55ee7…8ecc
0xa6afd3…d132
6 touches
3 conflicts
0x7506443a…4820
0x34b655…2a6f
6 touches
3 conflicts
0xd3ef5630…0de9
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity