← previous blocknext block →recent activity
Analyzing
Block #78,362,868
10 transactions · 9 stateful · 2026-06-01 05:57:21 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #78,362,868 · 10 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x21df8517…9a52
0x065c9d…c394
2 touches
0 conflicts
0x4d395e2d…6889
0x065c9d…c394
2 touches
0 conflicts
0x9cbb3d54…54e1
0x065c9d…c394
2 touches
0 conflicts
0xb3405089…abd4
0x065c9d…c394
2 touches
0 conflicts
0xf42c3409…1ca5
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