← previous blocknext block →recent activity
Analyzing
Block #84,046,051
29 transactions · 26 stateful · 2026-06-27 14:00:56 UTC
Parallelism
83/100
Blocked
31%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,046,051 · 29 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
1w04w15w213w014w117w221w322w324w427w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff96dc9b…93d7
0x065c9d…c394
8 touches
6 conflicts
0x0b16149e…7d4d
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd6f12d75…cd09
0xd32edf…ff58
5 touches
3 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
4 touches
1 conflict
0x92339d95…0800
0x0000a8…8888
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
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
6 conflicts on slot 0xff96dc9b2f…5a93d7
Audit this contract →
← previous block·next block →recent activity