pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,343,464
25 transactions · 17 stateful · 2026-05-08 23:49:45 UTC
Parallelism
80/100
Blocked
59%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,343,464 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w29w011w312w417w118w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a613b66…e1d1
0xd32edf…ff58
9 touches
10 conflicts
0xbdff944d…447e
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xd6e95dfc…bc65
0x065c9d…c394
5 touches
3 conflicts
0xf537eaa0…73c8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
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
10 conflicts on slot 0x1a613b6673…0ee1d1
Audit this contract →
← previous block·next block →recent activity