← previous blocknext block →recent activity
Analyzing
Block #80,477,410
16 transactions · 16 stateful · 2026-06-11 01:11:06 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,477,410 · 16 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
1w02w13w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x8707e1cb…080d
0x065c9d…c394
3 touches
1 conflict
0x2f26731e…4212
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0001
0x453805…c7fd
2 touches
0 conflicts
0x00000000…0002
0x453805…c7fd
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