← previous blocknext block →recent activity
Analyzing
Block #80,226,590
21 transactions · 14 stateful · 2026-06-09 21:19:14 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,226,590 · 21 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
1w02w14w25w06w37w311w015w118w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52d65d97…1c96
0xa6afd3…d132
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x8c0e6fca…c079
0xa6afd3…d132
5 touches
3 conflicts
0x40c9380a…2115
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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: 0xa6afd386…b0d132
3 conflicts on slot 0x52d65d97d4…d01c96
Audit this contract →
← previous block·next block →recent activity