← previous blocknext block →recent activity
Analyzing
Block #85,412,677
15 transactions · 13 stateful · 2026-07-03 21:51:05 UTC
Parallelism
73/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,412,677 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30faf03c…78b1
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x86f2922b…db07
0x0555e3…2b9c
2 touches
0 conflicts
0x91738a40…a23a
0x0555e3…2b9c
2 touches
0 conflicts
0x3f1434d4…1ce1
0x11ed3b…2c96
2 touches
0 conflicts
0x87b7c128…4c75
0x11ed3b…2c96
2 touches
0 conflicts
0x00000000…0003
0x175f44…559b
2 touches
0 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
3 conflicts on slot 0x30faf03c2d…0178b1
Audit this contract →
← previous block·next block →recent activity