pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,923,777
20 transactions · 18 stateful · 2026-05-11 16:28:05 UTC
Parallelism
60/100
Blocked
61%
Avg conflicts / tx
1.75
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,923,777 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w610w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d5f4089…4e8a
0x3bd359…433a
16 touches
28 conflicts
0x44ad89ba…cf83
0xd7c1ef…7777
16 touches
28 conflicts
0xd50086ec…092b
0xd7c1ef…7777
16 touches
28 conflicts
0x00000000…0001
0xd5bf41…8148
16 touches
28 conflicts
0xa472d565…9fe4
0x3bd359…433a
16 touches
28 conflicts
0x00000000…0000
0xd5bf41…8148
16 touches
28 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
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: 0x3bd359c1…15433a
28 conflicts on slot 0x2d5f408955…fa4e8a
Audit this contract →
← previous block·next block →recent activity