← previous blocknext block →recent activity
Analyzing
Block #80,971,925
16 transactions · 15 stateful · 2026-06-13 08:09:16 UTC
Parallelism
50/100
Blocked
47%
Avg conflicts / tx
1.75
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #80,971,925 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w410w511w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44ad89ba…cf83
0x7a481e…7777
16 touches
28 conflicts
0x5ee8860e…dca0
0x7a481e…7777
16 touches
28 conflicts
0x23e8605b…74ef
0x3bd359…433a
16 touches
28 conflicts
0x00000000…0000
0xaf7436…1e38
16 touches
28 conflicts
0x00000000…0001
0xaf7436…1e38
16 touches
28 conflicts
0x00000000…0003
0xaf7436…1e38
16 touches
28 conflicts
0xa472d565…9fe4
0x3bd359…433a
16 touches
28 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
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: 0x7a481e55…237777
28 conflicts on slot 0x44ad89ba62…49cf83
Audit this contract →
← previous block·next block →recent activity