← previous blocknext block →recent activity
Analyzing
Block #84,458,620
14 transactions · 11 stateful · 2026-06-29 11:49:33 UTC
Parallelism
79/100
Blocked
45%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,458,620 · 14 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
2w05w06w17w08w19w210w113w1
- 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
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x67d90e9f…c96e
0x065c9d…c394
4 touches
1 conflict
0xe75cebb6…6b36
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xab86573c…682e
0x34b655…2a6f
4 touches
1 conflict
0x2aafc1af…7138
0x065c9d…c394
3 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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity