← previous blocknext block →recent activity
Analyzing
Block #84,574,566
11 transactions · 11 stateful · 2026-06-30 00:43:26 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,574,566 · 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
1w02w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x56785e37…a197
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xe77e6653…42a4
0x065c9d…c394
4 touches
1 conflict
0x32f9c1ec…9a63
0x065c9d…c394
4 touches
1 conflict
0x0ed4bde3…902a
0x065c9d…c394
3 touches
1 conflict
0xcd1b430e…0986
0x065c9d…c394
3 touches
1 conflict
0xf8a0cebb…b351
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: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity