← previous blocknext block →recent activity
Analyzing
Block #80,309,629
20 transactions · 17 stateful · 2026-06-10 06:33:01 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,309,629 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w47w58w59w013w419w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x9ff176a9…152e
0x065c9d…c394
6 touches
3 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb1f0701d…4f4a
0xc8689a…ee79
4 touches
1 conflict
0xf5310ef7…485a
0x40c49f…2af0
4 touches
1 conflict
0x06e40499…165e
0x69df8a…6292
4 touches
1 conflict
0xa605468c…1bfc
0x69df8a…6292
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: MarginAccount
6 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity