← previous blocknext block →recent activity
Analyzing
Block #80,604,744
22 transactions · 19 stateful · 2026-06-11 15:20:45 UTC
Parallelism
77/100
Blocked
37%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,604,744 · 22 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
2w03w04w18w09w110w012w217w018w119w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x9cf5ac50…1be9
0xa6afd3…d132
6 touches
3 conflicts
0xbaff104b…3edb
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xca2926e0…61b5
0x34b655…2a6f
4 touches
1 conflict
0xd1e4de02…07e9
0x34b655…2a6f
4 touches
1 conflict
0xd9ad473c…92df
0x34b655…2a6f
4 touches
1 conflict
0xecb2b88e…24c8
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: Perpl
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity