← previous blocknext block →recent activity
Analyzing
Block #80,157,230
24 transactions · 22 stateful · 2026-06-09 13:36:45 UTC
Parallelism
75/100
Blocked
32%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,157,230 · 24 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
3w04w19w013w217w119w220w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7504b70b…f5ea
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x25de453d…9573
0x34b655…2a6f
4 touches
1 conflict
0x3fa47c90…0ce2
0x34b655…2a6f
4 touches
1 conflict
0x5c5c97c1…2fb0
0x34b655…2a6f
4 touches
1 conflict
0x8caf9cce…24a6
0x34b655…2a6f
4 touches
1 conflict
0x94a3fb3f…7515
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