← previous blocknext block →recent activity
Analyzing
Block #84,005,879
18 transactions · 16 stateful · 2026-06-27 09:33:18 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,005,879 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w36w410w011w113w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x6c538813…b007
0x065c9d…c394
6 touches
3 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
6 touches
3 conflicts
0x91220b8f…7a04
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xec1be274…a391
0xd32edf…ff58
5 touches
3 conflicts
0xd8e6aacd…1b57
0x40c49f…2af0
5 touches
3 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
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity