← previous blocknext block →recent activity
Analyzing
Block #85,182,457
14 transactions · 13 stateful · 2026-07-02 20:17:41 UTC
Parallelism
64/100
Blocked
46%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,182,457 · 14 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
1w02w13w24w05w16w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x822f8512…68e0
0x34b655…2a6f
8 touches
6 conflicts
0x88451e43…5a97
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x0a6f5e37…6c3c
0x34b655…2a6f
4 touches
1 conflict
0x0efc210e…70ab
0x34b655…2a6f
4 touches
1 conflict
0x278c656d…7716
0x34b655…2a6f
4 touches
1 conflict
0x3d34f2bd…5d63
0x34b655…2a6f
4 touches
1 conflict
0x5a8b47f0…7fbd
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 0x822f8512e8…4668e0
Audit this contract →
← previous block·next block →recent activity