pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,386,764
12 transactions · 10 stateful · 2026-05-09 04:37:46 UTC
Parallelism
58/100
Blocked
40%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,386,764 · 12 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
1w05w06w17w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0xabe9a5e3…6cf8
0x065c9d…c394
3 touches
1 conflict
0x44895203…c61c
0x065c9d…c394
2 touches
0 conflicts
0x47be9b97…4e23
0x065c9d…c394
2 touches
0 conflicts
0xa90ba2e4…f81a
0x065c9d…c394
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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: 0x2a68ba18…8e90c5
10 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity