← previous blocknext block →recent activity
Analyzing
Block #85,629,580
10 transactions · 9 stateful · 2026-07-04 21:55:15 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,629,580 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0x3793dc52…110c
0x34b655…2a6f
4 touches
1 conflict
0xe5d86b0a…98b7
0x40c49f…2af0
3 touches
1 conflict
0x79e45bd8…5d05
0x34b655…2a6f
3 touches
1 conflict
0x01285452…3d69
0x40c49f…2af0
2 touches
0 conflicts
0xa3f57322…ee18
0x40c49f…2af0
2 touches
0 conflicts
0xad2d703a…6879
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 0xafd867b7ed…d92b2d
Audit this contract →
← previous block·next block →recent activity