← previous blocknext block →recent activity
Analyzing
Block #78,361,948
14 transactions · 11 stateful · 2026-06-01 05:51:15 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #78,361,948 · 14 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
1w02w13w25w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x261e21f6…435e
0x2a68ba…90c5
2 touches
1 conflict
0xc3174a06…6a8b
0x754704…b603
2 touches
1 conflict
0x05fbf9fb…46cb
0x065c9d…c394
2 touches
0 conflicts
0x134e56f1…a3ef
0x065c9d…c394
2 touches
0 conflicts
0x4f75c475…8ed3
0x065c9d…c394
2 touches
0 conflicts
0x52e69143…95ad
0x065c9d…c394
2 touches
0 conflicts
0xa89df366…2370
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity