← previous blocknext block →recent activity
Analyzing
Block #80,822,591
89 transactions · 75 stateful · 2026-06-12 15:33:36 UTC
Parallelism
78/100
Blocked
81%
Avg conflicts / tx
4
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #80,822,591 · 89 txs across 20 waves · depth 20
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w16w09w112w013w218w219w220w324w327w428w529w631w871w772w873w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
26 touches
78 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
24 touches
66 conflicts
0x00000000…0002
0x6fae99…a56d
22 touches
55 conflicts
0xfe1362cf…bb85
0xa6afd3…d132
20 touches
45 conflicts
0x00000000…003d
0xa6afd3…d132
18 touches
36 conflicts
0xdb067026…9eb8
0x69df8a…6292
18 touches
36 conflicts
0x1504aa7b…24ad
0xa6afd3…d132
18 touches
36 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
78 conflicts on slot 0x90f07a4ff9…b3d932
Audit this contract →
← previous block·next block →recent activity