← previous blocknext block →recent activity
Analyzing
Block #85,345,221
32 transactions · 21 stateful · 2026-07-03 14:21:47 UTC
Parallelism
78/100
Blocked
57%
Avg conflicts / tx
0.97
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,345,221 · 32 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w27w213w014w115w216w317w418w222w523w327w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc68d6f14…bdde
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x9fb55ee7…8ecc
0xa6afd3…d132
8 touches
6 conflicts
0xebda062f…e87a
0x34b655…2a6f
8 touches
6 conflicts
0x26470289…bb21
0xa6afd3…d132
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x40970e69…da50
0x69df8a…6292
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 0xc68d6f1433…40bdde
Audit this contract →
← previous block·next block →recent activity