pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,200,649
8 transactions · 7 stateful · 2026-05-08 07:59:41 UTC
Parallelism
50/100
Blocked
43%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,200,649 · 8 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f05571a…68e9
0xd32edf…ff58
7 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x00c4a84f…a743
0x065c9d…c394
2 touches
0 conflicts
0x355c189a…66a9
0x065c9d…c394
2 touches
0 conflicts
0x652ba222…02b1
0x065c9d…c394
2 touches
0 conflicts
0x89bcddb5…2af4
0x065c9d…c394
2 touches
0 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: 0xd32edf66…9fff58
6 conflicts on slot 0x0f05571ae9…4c68e9
Audit this contract →
← previous block·next block →recent activity