← previous blocknext block →recent activity
Analyzing
Block #80,971,913
18 transactions · 14 stateful · 2026-06-13 08:09:11 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,971,913 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w110w011w112w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0003
0xaf7436…1e38
12 touches
15 conflicts
0x23e8605b…74ef
0x3bd359…433a
12 touches
15 conflicts
0xa472d565…9fe4
0x3bd359…433a
12 touches
15 conflicts
0x44ad89ba…cf83
0x7a481e…7777
12 touches
15 conflicts
0x5ee8860e…dca0
0x7a481e…7777
12 touches
15 conflicts
0x00000000…0000
0xaf7436…1e38
12 touches
15 conflicts
0x00000000…0001
0xaf7436…1e38
12 touches
15 conflicts
0x9a3068dd…18f1
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: 0xaf74363e…281e38
15 conflicts on slot 0x0000000000…000003
Audit this contract →
← previous block·next block →recent activity