← previous blocknext block →recent activity
Analyzing
Block #78,363,490
12 transactions · 11 stateful · 2026-06-01 06:01:28 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #78,363,490 · 12 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
1w02w13w24w310w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x2b837549…0d3f
0x065c9d…c394
4 touches
1 conflict
0x3873ee2f…4dc2
0x065c9d…c394
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x7e62761a…2248
0x065c9d…c394
4 touches
1 conflict
0x904c1371…3699
0x065c9d…c394
4 touches
1 conflict
0xa60aedce…0518
0x065c9d…c394
4 touches
1 conflict
0xae2c1987…6442
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity