← previous blocknext block →recent activity
Analyzing
Block #80,068,381
25 transactions · 22 stateful · 2026-06-09 03:45:03 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,068,381 · 25 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
3w05w16w07w28w311w012w113w214w317w420w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde6b917f…3a72
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xb0e9898d…42c2
0xa6afd3…d132
6 touches
3 conflicts
0x90f07a4f…d932
0x34b655…2a6f
6 touches
3 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x55579de4…0ccf
0x34b655…2a6f
4 touches
1 conflict
0x7504b70b…f5ea
0x34b655…2a6f
4 touches
1 conflict
0x761df496…a7b7
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: 0xa6afd386…b0d132
6 conflicts on slot 0xde6b917faa…a83a72
Audit this contract →
← previous block·next block →recent activity