← previous blocknext block →recent activity
Analyzing
Block #73,375,652
66 transactions · 47 stateful · 2026-05-09 03:23:52 UTC
Parallelism
76/100
Blocked
68%
Avg conflicts / tx
1.76
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #73,375,652 · 66 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
1w03w14w26w07w18w09w315w118w019w130w031w132w233w134w235w336w437w538w648w249w351w1
- 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
14 touches
21 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
14 touches
21 conflicts
0xd49762c9…1359
0x34b655…2a6f
12 touches
15 conflicts
0x57de3828…3fbb
0x34b655…2a6f
10 touches
10 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
10 touches
10 conflicts
0x908d4442…2c4b
0x34b655…2a6f
10 touches
10 conflicts
0x99f080dc…58c1
0x34b655…2a6f
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