← previous blocknext block →recent activity
Analyzing
Block #85,103,973
15 transactions · 13 stateful · 2026-07-02 11:33:57 UTC
Parallelism
73/100
Blocked
23%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,103,973 · 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
6w010w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x79b3209b…f766
0x34b655…2a6f
6 touches
3 conflicts
0x747f609d…1555
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x353a3a00…5e0a
0x34b655…2a6f
3 touches
1 conflict
0x26e741e7…0088
0x34b655…2a6f
2 touches
0 conflicts
0x2a00eaec…dce0
0x34b655…2a6f
2 touches
0 conflicts
0x678a8de3…7da5
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity