pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,288,099
46 transactions · 33 stateful · 2026-05-04 02:41:16 UTC
Parallelism
67/100
Blocked
70%
Avg conflicts / tx
2.17
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #72,288,099 · 46 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w113w114w018w019w120w221w322w423w524w625w726w827w928w1029w1134w139w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
24 touches
66 conflicts
0xc6417de0…2191
0xc8689a…ee79
10 touches
10 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
10 touches
10 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
10 touches
10 conflicts
0x9be2b99a…a959
0x34b655…2a6f
10 touches
10 conflicts
0x9cc607d0…c9c7
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
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: 0x34b6552d…112a6f
66 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity