← previous blocknext block →recent activity
Analyzing
Block #85,914,612
30 transactions · 22 stateful · 2026-07-06 05:34:43 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.37
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,914,612 · 30 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
1w03w04w15w213w114w015w120w221w324w427w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x58866db9…f0d5
0x065c9d…c394
6 touches
3 conflicts
0xb33ff823…1188
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa2ac3fa8…ff59
0x065c9d…c394
5 touches
3 conflicts
0xe16b9d73…8dd0
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x66f473d3…2d03
0xa6afd3…d132
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity