← previous blocknext block →recent activity
Analyzing
Block #85,568,915
22 transactions · 20 stateful · 2026-07-04 15:11:15 UTC
Parallelism
77/100
Blocked
55%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,568,915 · 22 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
1w02w03w14w26w38w19w010w111w212w313w414w415w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11d629eb…bcd9
0x34b655…2a6f
10 touches
10 conflicts
0x45597879…8174
0x34b655…2a6f
10 touches
10 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
10 touches
10 conflicts
0x757b0543…e087
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x202c03eb…cf33
0xa6afd3…d132
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xdec5bfea…d17f
0xa6afd3…d132
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 0x11d629ebd0…9fbcd9
Audit this contract →
← previous block·next block →recent activity