pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,399,205
47 transactions · 38 stateful · 2026-05-04 15:01:55 UTC
Parallelism
77/100
Blocked
68%
Avg conflicts / tx
2.17
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #72,399,205 · 47 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
1w02w13w04w16w27w013w216w018w119w220w321w425w026w127w228w329w438w139w240w341w342w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xbad68552…e6bf
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0x7e9d3a…9fda
10 touches
10 conflicts
0x24968e6d…0132
0x065c9d…c394
8 touches
6 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
8 touches
6 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
8 touches
6 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
55 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity