← previous blocknext block →recent activity
Analyzing
Block #84,526,598
30 transactions · 25 stateful · 2026-06-29 19:23:05 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,526,598 · 30 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
2w03w05w07w19w014w015w116w120w121w222w223w324w225w426w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
8 touches
6 conflicts
0x56785e37…a197
0x065c9d…c394
8 touches
6 conflicts
0x4ca4efa9…d863
0xd32edf…ff58
5 touches
3 conflicts
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x393dfd73…ff57
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0xdee0bd3a…7bea
0x34b655…2a6f
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity