← previous blocknext block →recent activity
Analyzing
Block #80,165,604
22 transactions · 21 stateful · 2026-06-09 14:32:37 UTC
Parallelism
77/100
Blocked
29%
Avg conflicts / tx
0.32
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,165,604 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w312w013w114w015w417w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x36d366fe…7adc
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xf5310ef7…485a
0x40c49f…2af0
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xef65bff3…7c9d
0x2a68ba…90c5
4 touches
1 conflict
0x90f07a4f…d932
0x34b655…2a6f
4 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: 0x40c49f17…d22af0
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity