← previous blocknext block →recent activity
Analyzing
Block #80,264,647
17 transactions · 13 stateful · 2026-06-10 01:33:10 UTC
Parallelism
76/100
Blocked
23%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,264,647 · 17 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
4w05w06w17w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x36d366fe…7adc
0xa6afd3…d132
6 touches
3 conflicts
0x1d066559…5d89
0xa6afd3…d132
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x7531e9d9…196d
0xa6afd3…d132
4 touches
1 conflict
0xeaaa7cbb…be0b
0xa6afd3…d132
3 touches
1 conflict
0x50cbae8c…422d
0xa6afd3…d132
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: 0xa6afd386…b0d132
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity