← previous blocknext block →recent activity
Analyzing
Block #80,157,504
15 transactions · 12 stateful · 2026-06-09 13:38:35 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,157,504 · 15 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
1w02w13w24w06w09w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37ff1602…9135
0x065c9d…c394
4 touches
2 conflicts
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xe1d1f14d…3ffb
0x34b655…2a6f
4 touches
1 conflict
0xfffc81b0…3b47
0x065c9d…c394
3 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
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
2 conflicts on slot 0x37ff1602ce…a49135
Audit this contract →
← previous block·next block →recent activity