← previous blocknext block →recent activity
Analyzing
Block #85,825,055
18 transactions · 12 stateful · 2026-07-05 19:38:07 UTC
Parallelism
78/100
Blocked
42%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,825,055 · 18 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
1w02w17w08w115w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x7ea53c99…0c3e
0x34b655…2a6f
4 touches
1 conflict
0x139930c4…2d6c
0xd32edf…ff58
3 touches
1 conflict
0xdb067026…9eb8
0x69df8a…6292
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0xe2263bea…6a9f
0x69df8a…6292
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity