← previous blocknext block →recent activity
Analyzing
Block #80,553,563
20 transactions · 14 stateful · 2026-06-11 09:38:30 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,553,563 · 20 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
1w02w13w05w16w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x8abcf3a9…5992
0x065c9d…c394
3 touches
1 conflict
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x46b84b21…b77c
0x40c49f…2af0
2 touches
0 conflicts
0xbd04e5f4…e233
0x40c49f…2af0
2 touches
0 conflicts
0xe7a52243…fbef
0x40c49f…2af0
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 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity