← previous blocknext block →recent activity
Analyzing
Block #80,500,824
10 transactions · 10 stateful · 2026-06-11 03:47:01 UTC
Parallelism
50/100
Blocked
40%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,500,824 · 10 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x21898044…a071
0x065c9d…c394
6 touches
3 conflicts
0x40ecf911…c755
0x065c9d…c394
4 touches
1 conflict
0x1a53f097…ad9f
0x065c9d…c394
2 touches
0 conflicts
0x208fd370…42d4
0x065c9d…c394
2 touches
0 conflicts
0x2a945db4…af56
0x065c9d…c394
2 touches
0 conflicts
0x2de8069a…e431
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
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity