← previous blocknext block →recent activity
Analyzing
Block #84,358,011
37 transactions · 29 stateful · 2026-06-29 00:39:03 UTC
Parallelism
84/100
Blocked
55%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,358,011 · 37 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
1w02w13w04w18w210w012w013w114w115w016w119w020w121w223w224w225w326w327w429w430w535w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xe75cebb6…6b36
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xd637b3…4160
6 touches
3 conflicts
0x56785e37…a197
0x065c9d…c394
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 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: Market-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity