← previous blocknext block →recent activity
Analyzing
Block #85,199,327
12 transactions · 11 stateful · 2026-07-02 22:10:00 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,199,327 · 12 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
1w02w13w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc99e7125…81b1
0x34b655…2a6f
4 touches
1 conflict
0xd63e616b…a07d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x7204a5b8…b1d5
0x34b655…2a6f
4 touches
1 conflict
0x68738f09…17e4
0x40c49f…2af0
2 touches
0 conflicts
0xd5836ed2…2d03
0x40c49f…2af0
2 touches
0 conflicts
0xfab1b240…9bf9
0x40c49f…2af0
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 0xc99e71253c…e381b1
Audit this contract →
← previous block·next block →recent activity