← previous blocknext block →recent activity
Analyzing
Block #84,451,354
12 transactions · 12 stateful · 2026-06-29 11:01:08 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,451,354 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x5df6102c…6494
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7cb39717…2a75
0x065c9d…c394
2 touches
0 conflicts
0xb06b47e6…7378
0x065c9d…c394
2 touches
0 conflicts
0xd3772444…13b9
0x065c9d…c394
2 touches
0 conflicts
0xf103a7d8…badb
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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