← previous blocknext block →recent activity
Analyzing
Block #80,256,324
14 transactions · 11 stateful · 2026-06-10 00:37:39 UTC
Parallelism
86/100
Blocked
9%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,256,324 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
2 touches
0 conflicts
0x00f7e3b7…e016
0x188d58…ea8e
2 touches
0 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
2 touches
0 conflicts
0x99f666e3…b2a2
0x3bd359…433a
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x0e96c911…a213
0x40c49f…2af0
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
1 conflict on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity