← previous blocknext block →recent activity
Analyzing
Block #85,176,885
16 transactions · 16 stateful · 2026-07-02 19:40:31 UTC
Parallelism
81/100
Blocked
19%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,176,885 · 16 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
1w07w111w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x4abbc09d…ddb0
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
0xd63e616b…a07d
0x34b655…2a6f
4 touches
1 conflict
0x01345e18…e04d
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
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
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity