← previous blocknext block →recent activity
Analyzing
Block #78,362,575
18 transactions · 15 stateful · 2026-06-01 05:55:24 UTC
Parallelism
78/100
Blocked
20%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #78,362,575 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x3000f448…9034
0x065c9d…c394
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x85b03987…1bf7
0x2a68ba…90c5
3 touches
1 conflict
0x731519ad…f215
0x065c9d…c394
2 touches
0 conflicts
0xa38ec486…2db5
0x065c9d…c394
2 touches
0 conflicts
0xc88bb07c…3517
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity