← previous blocknext block →recent activity
Analyzing
Block #80,296,432
11 transactions · 8 stateful · 2026-06-10 05:04:58 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,296,432 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w07w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb424694f…8c5d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0x32194857…8418
0x065c9d…c394
3 touches
1 conflict
0x139b3330…d1b1
0x065c9d…c394
3 touches
1 conflict
0x7cc5cc1a…e1ce
0x065c9d…c394
3 touches
1 conflict
0xa22b3a57…5bce
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: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity