← previous blocknext block →recent activity
Analyzing
Block #85,983,161
27 transactions · 23 stateful · 2026-07-06 13:12:01 UTC
Parallelism
85/100
Blocked
48%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,983,161 · 27 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
1w02w13w04w15w26w07w114w115w216w319w320w321w225w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd16df6cd…5532
0x40c49f…2af0
6 touches
3 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
6 touches
3 conflicts
0x7e10454f…4d9e
0xa6afd3…d132
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x8a751d7a…247c
0xa6afd3…d132
6 touches
3 conflicts
0xe39c11d9…b9f4
0x065c9d…c394
5 touches
3 conflicts
0xd98b3c10…67b8
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
3 conflicts on slot 0xd16df6cdbe…065532
Audit this contract →
← previous block·next block →recent activity