pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,651,609
13 transactions · 13 stateful · 2026-05-10 10:01:59 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,651,609 · 13 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
2w04w05w17w210w312w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56c38ae3…d667
0xd32edf…ff58
5 touches
3 conflicts
0x0ac31945…2c72
0x065c9d…c394
4 touches
1 conflict
0xf2438038…5fa7
0x34b655…2a6f
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0xf6802cf0…344f
0x000000…012a
2 touches
0 conflicts
0x00000000…0000
0x16d564…365f
2 touches
0 conflicts
0x00000000…0002
0x16d564…365f
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
3 conflicts on slot 0x56c38ae3b4…47d667
Audit this contract →
← previous block·next block →recent activity