← previous blocknext block →recent activity
Analyzing
Block #73,663,673
47 transactions · 43 stateful · 2026-05-10 11:23:17 UTC
Parallelism
57/100
Blocked
81%
Avg conflicts / tx
4.47
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #73,663,673 · 47 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
1w02w13w24w37w213w314w432w433w534w635w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa91c899f…6ee3
0x34b655…2a6f
30 touches
105 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
24 touches
66 conflicts
0x64e30b79…bc29
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xc6417de0…2191
0xc8689a…ee79
18 touches
36 conflicts
0xedb848fe…6534
0x34b655…2a6f
18 touches
36 conflicts
0x908d4442…2c4b
0x34b655…2a6f
18 touches
36 conflicts
0x57de3828…3fbb
0x34b655…2a6f
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
105 conflicts on slot 0xa91c899f02…fa6ee3
Audit this contract →
← previous block·next block →recent activity