← previous blocknext block →recent activity
Analyzing
Block #78,363,540
16 transactions · 12 stateful · 2026-06-01 06:01:48 UTC
Parallelism
56/100
Blocked
58%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #78,363,540 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w512w413w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52e69143…95ad
0x065c9d…c394
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xce827910…ff22
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb1f0701d…4f4a
0xc8689a…ee79
4 touches
1 conflict
0x2cd408d4…a589
0x065c9d…c394
4 touches
1 conflict
0x5bd6e800…3777
0x065c9d…c394
4 touches
1 conflict
0xb90abd10…416c
0x065c9d…c394
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 0x52e6914362…6e95ad
Audit this contract →
← previous block·next block →recent activity