← previous blocknext block →recent activity
Analyzing
Block #80,971,881
16 transactions · 13 stateful · 2026-06-13 08:08:58 UTC
Parallelism
69/100
Blocked
54%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,971,881 · 16 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
1w06w07w18w29w310w413w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ee8860e…dca0
0x7a481e…7777
10 touches
10 conflicts
0x00000000…0001
0xaf7436…1e38
10 touches
10 conflicts
0x00000000…0003
0xaf7436…1e38
10 touches
10 conflicts
0x00000000…0000
0xaf7436…1e38
10 touches
10 conflicts
0x23e8605b…74ef
0x3bd359…433a
10 touches
10 conflicts
0xa472d565…9fe4
0x3bd359…433a
10 touches
10 conflicts
0x44ad89ba…cf83
0x7a481e…7777
10 touches
10 conflicts
0xd68cd74f…9826
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x5ee8860e36…9edca0
Audit this contract →
← previous block·next block →recent activity