← previous blocknext block →recent activity
Analyzing
Block #80,164,305
20 transactions · 16 stateful · 2026-06-09 14:23:58 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,164,305 · 20 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
1w05w16w27w310w011w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0xb1f0701d…4f4a
0xc8689a…ee79
6 touches
3 conflicts
0x033cf007…136d
0x34b655…2a6f
6 touches
3 conflicts
0x66812b79…4c80
0x34b655…2a6f
6 touches
3 conflicts
0x06e40499…165e
0x69df8a…6292
6 touches
3 conflicts
0xa605468c…1bfc
0x69df8a…6292
6 touches
3 conflicts
0xc938a66c…cc09
0x065c9d…c394
5 touches
3 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