← previous blocknext block →recent activity
Analyzing
Block #84,570,066
11 transactions · 7 stateful · 2026-06-30 00:13:25 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,570,066 · 11 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
1w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x63aed433…e03e
0x40c49f…2af0
3 touches
1 conflict
0x00000000…009a
0x16f70c…c3dd
2 touches
0 conflicts
0x72a152dd…9edd
0x16f70c…c3dd
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
2 touches
0 conflicts
0x88bacd3e…22f9
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity