← previous blocknext block →recent activity
Analyzing
Block #73,642,721
40 transactions · 30 stateful · 2026-05-10 09:02:09 UTC
Parallelism
73/100
Blocked
70%
Avg conflicts / tx
1.9
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #73,642,721 · 40 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w612w013w414w117w230w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa91c899f…6ee3
0x34b655…2a6f
18 touches
36 conflicts
0xab41bf9c…66a9
0x34b655…2a6f
16 touches
28 conflicts
0x4bae123b…95fd
0xd32edf…ff58
13 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xedb848fe…6534
0x34b655…2a6f
12 touches
15 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0xc6417de0…2191
0xc8689a…ee79
12 touches
15 conflicts
0x1b9e654e…0a08
0x34b655…2a6f
12 touches
15 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 0xa91c899f02…fa6ee3
Audit this contract →
← previous block·next block →recent activity