← previous blocknext block →recent activity
Analyzing
Block #84,179,517
12 transactions · 12 stateful · 2026-06-28 04:49:39 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,179,517 · 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
1w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b16149e…7d4d
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1a827f59…1e15
0x065c9d…c394
2 touches
0 conflicts
0x56785e37…a197
0x065c9d…c394
2 touches
0 conflicts
0x88ea11e0…2c0d
0x065c9d…c394
2 touches
0 conflicts
0xabda38f8…60f6
0x065c9d…c394
2 touches
0 conflicts
0xb7eff691…8166
0x065c9d…c394
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 0x0b16149e0d…887d4d
Audit this contract →
← previous block·next block →recent activity