← previous blocknext block →recent activity
Analyzing
Block #80,166,238
25 transactions · 21 stateful · 2026-06-09 14:36:51 UTC
Parallelism
76/100
Blocked
52%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,166,238 · 25 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
1w02w05w06w17w18w29w010w213w316w119w120w221w322w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x2495fdde…5ee9
0x34b655…2a6f
6 touches
3 conflicts
0xf853eb8e…4027
0x34b655…2a6f
6 touches
3 conflicts
0x7531e9d9…196d
0xa6afd3…d132
6 touches
3 conflicts
0x5ba4db2b…2f04
0x34b655…2a6f
4 touches
1 conflict
0x7cbd466f…1700
0x34b655…2a6f
4 touches
1 conflict
0x8db1e0f2…2fcf
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