← previous blocknext block →recent activity
Analyzing
Block #85,182,979
20 transactions · 17 stateful · 2026-07-02 20:21:10 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,182,979 · 20 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
2w03w19w010w011w212w114w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96d3f10e…4950
0x40c49f…2af0
4 touches
1 conflict
0xd16df6cd…5532
0x40c49f…2af0
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x379a09c4…259b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3e1c3586…83d7
0xa6afd3…d132
4 touches
1 conflict
0x987aeb55…0e2a
0xa6afd3…d132
4 touches
1 conflict
0x88451e43…5a97
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: 0x40c49f17…d22af0
1 conflict on slot 0x96d3f10ef7…124950
Audit this contract →
← previous block·next block →recent activity