← previous blocknext block →recent activity
Analyzing
Block #80,340,408
9 transactions · 9 stateful · 2026-06-10 09:58:13 UTC
Parallelism
56/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,340,408 · 9 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
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x7b9a42f7…7b88
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0000
0x24b18e…3301
2 touches
0 conflicts
0x00000000…0001
0x24b18e…3301
2 touches
0 conflicts
0x24cfe713…0f91
0x25d593…7777
2 touches
0 conflicts
0x44ad89ba…cf83
0x25d593…7777
2 touches
0 conflicts
0x00000000…0000
0x30611e…d8d9
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
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity