pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,501,033
14 transactions · 13 stateful · 2026-05-09 17:18:16 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,501,033 · 14 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
4w05w16w27w38w412w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x3704e4…e36f
10 touches
10 conflicts
0x8b144217…a58e
0xb68427…7777
10 touches
10 conflicts
0x44ad89ba…cf83
0xb68427…7777
10 touches
10 conflicts
0xea8e8e68…ba34
0x3bd359…433a
10 touches
10 conflicts
0xa472d565…9fe4
0x3bd359…433a
10 touches
10 conflicts
0x00000000…0001
0x3704e4…e36f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0462262d…a368
0x34b655…2a6f
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: 0x3704e421…3ae36f
10 conflicts on slot 0x0000000000…000000
Audit this contract →
← previous block·next block →recent activity