← previous blocknext block →recent activity
Analyzing
Block #84,253,786
17 transactions · 16 stateful · 2026-06-28 13:04:32 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,253,786 · 17 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
1w04w06w18w19w010w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7b7af531…48f1
0xa6afd3…d132
4 touches
1 conflict
0x8e739938…e7ab
0x34b655…2a6f
4 touches
1 conflict
0x5df6102c…6494
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity