← previous blocknext block →recent activity
Analyzing
Block #86,823,622
21 transactions · 21 stateful · 2026-07-10 10:48:45 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,823,622 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w210w011w213w315w318w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f4cddfd…3085
0x34b655…2a6f
10 touches
10 conflicts
0xf871d18f…979a
0x34b655…2a6f
8 touches
6 conflicts
0x13bf11f1…cbb2
0x34b655…2a6f
6 touches
3 conflicts
0x51b48435…3765
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x78f9dd3b…66e1
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 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 0x0f4cddfd7a…203085
Audit this contract →
← previous block·next block →recent activity