← previous blocknext block →recent activity
Analyzing
Block #80,328,628
29 transactions · 24 stateful · 2026-06-10 08:39:43 UTC
Parallelism
79/100
Blocked
58%
Avg conflicts / tx
1.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,328,628 · 29 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
2w03w14w25w36w07w18w210w011w113w416w017w118w219w324w025w226w327w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0001
0x24b18e…3301
8 touches
6 conflicts
0x57a080db…7fde
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0000
0x24b18e…3301
8 touches
6 conflicts
0x771a3650…01cd
0x3bd359…433a
8 touches
6 conflicts
0x797464db…e15a
0x788571…8888
8 touches
6 conflicts
0xa743c8dd…ebf2
0x788571…8888
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 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: Perpl
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity