← previous blocknext block →recent activity
Analyzing
Block #80,297,773
10 transactions · 10 stateful · 2026-06-10 05:13:55 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,297,773 · 10 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
1w02w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x1ab549da…6f31
0x065c9d…c394
2 touches
0 conflicts
0x60d67be4…56ab
0x065c9d…c394
2 touches
0 conflicts
0x837dc1f2…9341
0x065c9d…c394
2 touches
0 conflicts
0xe41bcb62…2ed1
0x065c9d…c394
2 touches
0 conflicts
0xeece21b9…1fa2
0x065c9d…c394
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity