← previous blocknext block →recent activity
Analyzing
Block #80,744,016
35 transactions · 13 stateful · 2026-06-12 06:49:40 UTC
Parallelism
89/100
Blocked
31%
Avg conflicts / tx
0.17
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,744,016 · 35 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
1w02w09w110w211w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x342fbbca…d443
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5673d5f8…d638
0x40c49f…2af0
2 touches
0 conflicts
0xe181a6d1…a267
0x40c49f…2af0
2 touches
0 conflicts
0xffa7d0a4…b10a
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
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity