← previous blocknext block →recent activity
Analyzing
Block #75,729,110
50 transactions · 38 stateful · 2026-05-20 01:24:38 UTC
Parallelism
68/100
Blocked
74%
Avg conflicts / tx
2.58
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #75,729,110 · 50 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w18w29w010w014w017w120w021w122w223w324w425w526w627w728w833w334w436w638w740w141w242w843w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0xb7b446d2…2006
0x34b655…2a6f
14 touches
21 conflicts
0xb569beea…9bea
0xd32edf…ff58
13 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0x9394e22c…3da3
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity