← previous blocknext block →recent activity
Analyzing
Block #80,328,874
32 transactions · 22 stateful · 2026-06-10 08:41:22 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,328,874 · 32 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
1w02w03w14w27w08w110w015w316w017w118w130w131w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4afaa2f…3b69
0xa6afd3…d132
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x7b9a42f7…7b88
0xa6afd3…d132
6 touches
3 conflicts
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0xfff39462…a61b
0x34b655…2a6f
4 touches
1 conflict
0x771a3650…01cd
0x3bd359…433a
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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
3 conflicts on slot 0xe4afaa2f27…943b69
Audit this contract →
← previous block·next block →recent activity