← previous blocknext block →recent activity
Analyzing
Block #80,642,231
40 transactions · 36 stateful · 2026-06-11 19:31:04 UTC
Parallelism
75/100
Blocked
64%
Avg conflicts / tx
1.88
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #80,642,231 · 40 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w09w110w211w323w625w528w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x936f37a8…9812
0xa6afd3…d132
10 touches
10 conflicts
0x90f07a4f…d932
0x34b655…2a6f
8 touches
6 conflicts
0xb409e204…89ac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity