← previous blocknext block →recent activity
Analyzing
Block #80,573,432
24 transactions · 19 stateful · 2026-06-11 11:51:28 UTC
Parallelism
92/100
Blocked
16%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,573,432 · 24 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w09w010w113w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0x84fb2a36…db89
0x34b655…2a6f
4 touches
1 conflict
0xc38151f2…2bcb
0xc8689a…ee79
4 touches
1 conflict
0xb138d087…4689
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xef1cbbb7…8cc8
0x34b655…2a6f
4 touches
1 conflict
0x3bd5c450…a1cd
0x065c9d…c394
3 touches
1 conflict
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: Market-MON/USDC
1 conflict on slot 0x160f117d43…518e90
Audit this contract →
← previous block·next block →recent activity