← previous blocknext block →recent activity
Analyzing
Block #80,157,464
23 transactions · 19 stateful · 2026-06-09 13:38:19 UTC
Parallelism
83/100
Blocked
26%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,157,464 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w26w17w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xde6b917f…3a72
0xa6afd3…d132
4 touches
1 conflict
0x565818b0…80a3
0xa6afd3…d132
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xcdc947e3…bfe5
0x065c9d…c394
3 touches
1 conflict
0x00000000…0006
0x010592…1c83
2 touches
0 conflicts
0x6a00472b…ac50
0x010592…1c83
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 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity