← previous blocknext block →recent activity
Analyzing
Block #85,361,740
17 transactions · 15 stateful · 2026-07-03 16:11:48 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,361,740 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w09w010w111w212w115w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda2ee2e7…968a
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x4bfbf321…d4f2
0x34b655…2a6f
4 touches
1 conflict
0x6db97e95…8353
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x84d74093…7808
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
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 0xda2ee2e777…e7968a
Audit this contract →
← previous block·next block →recent activity