← previous blocknext block →recent activity
Analyzing
Block #84,411,235
15 transactions · 13 stateful · 2026-06-29 06:33:49 UTC
Parallelism
87/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,411,235 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w19w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0xc47ca59a…b171
0x34b655…2a6f
4 touches
1 conflict
0x3b53f315…f397
0x065c9d…c394
2 touches
0 conflicts
0x54dca843…8726
0x065c9d…c394
2 touches
0 conflicts
0x8b6aa87e…c78b
0x065c9d…c394
2 touches
0 conflicts
0xc1e2d51d…f63e
0x065c9d…c394
2 touches
0 conflicts
0xc6638e5d…d1f7
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity