← previous blocknext block →recent activity
Analyzing
Block #85,177,229
14 transactions · 13 stateful · 2026-07-02 19:42:48 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,177,229 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w28w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb04d17a0…10e8
0x34b655…2a6f
4 touches
1 conflict
0xcffc17bc…3544
0x34b655…2a6f
4 touches
1 conflict
0x276f1d01…5d58
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x85631114…3ff6
0xa6afd3…d132
4 touches
1 conflict
0x987aeb55…0e2a
0xa6afd3…d132
4 touches
1 conflict
0x4d4d5f6d…8388
0xa6afd3…d132
4 touches
1 conflict
0x41e9f576…ca45
0xa6afd3…d132
3 touches
1 conflict
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
1 conflict on slot 0xb04d17a0fe…4810e8
Audit this contract →
← previous block·next block →recent activity