← previous blocknext block →recent activity
Analyzing
Block #85,569,021
24 transactions · 21 stateful · 2026-07-04 15:11:58 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,569,021 · 24 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
2w04w05w16w210w111w012w113w214w317w419w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6ed530e…fa7d
0x34b655…2a6f
10 touches
10 conflicts
0x757b0543…e087
0x34b655…2a6f
8 touches
6 conflicts
0x7b4c2b35…4d60
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
8 touches
6 conflicts
0xdec5bfea…d17f
0xa6afd3…d132
8 touches
6 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
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 0xc6ed530ecc…a9fa7d
Audit this contract →
← previous block·next block →recent activity