pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,353,261
33 transactions · 27 stateful · 2026-05-09 00:55:01 UTC
Parallelism
73/100
Blocked
48%
Avg conflicts / tx
0.97
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #73,353,261 · 33 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w08w110w213w215w124w325w426w527w628w729w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0x22e295f5…1bef
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0004
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0002
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
6 touches
3 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
6 touches
3 conflicts
0x4d87512b…897c
0x065c9d…c394
6 touches
3 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: 0x065c9d28…a9c394
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity