← previous blocknext block →recent activity
Analyzing
Block #85,920,792
14 transactions · 11 stateful · 2026-07-06 06:15:52 UTC
Parallelism
71/100
Blocked
27%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,920,792 · 14 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
1w02w13w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x42faeee9…1979
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe2fc7c84…7696
0x065c9d…c394
3 touches
1 conflict
0x2bc966c3…9545
0x065c9d…c394
3 touches
1 conflict
0x1014e8d4…1b95
0x40c49f…2af0
2 touches
0 conflicts
0x280c5ac2…a999
0x40c49f…2af0
2 touches
0 conflicts
0x6336a9ae…7677
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity