← previous blocknext block →recent activity
Analyzing
Block #80,315,976
21 transactions · 13 stateful · 2026-06-10 07:15:24 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,315,976 · 21 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
2w03w16w07w210w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x179fe783…6945
0xa6afd3…d132
4 touches
1 conflict
0xd3b961cb…02a4
0x40c49f…2af0
3 touches
1 conflict
0x00000000…0004
0x3f51f6…80d5
2 touches
0 conflicts
0x00000000…0009
0x3f51f6…80d5
2 touches
0 conflicts
0x40970e69…da50
0x69df8a…6292
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: MarginAccount
3 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity