← previous blocknext block →recent activity
Analyzing
Block #86,733,769
43 transactions · 37 stateful · 2026-07-10 00:48:18 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.28
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #86,733,769 · 43 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w17w08w19w210w011w112w214w015w116w217w218w319w420w528w731w332w336w937w1038w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0xa29182a1…c12c
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
8 touches
6 conflicts
0x8a35acfb…d1ac
0xb1dbf0…c0d3
8 touches
6 conflicts
0x0d2de0f6…e6c6
0x34b655…2a6f
8 touches
6 conflicts
0xac808a27…82db
0x34b655…2a6f
8 touches
6 conflicts
0xc201656f…548e
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity