pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,483,005
15 transactions · 14 stateful · 2026-05-09 15:18:13 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,483,005 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w08w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb06c5ce4…99c7
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0x049c4dda…51a2
0x065c9d…c394
2 touches
0 conflicts
0x0b390c61…dc07
0x065c9d…c394
2 touches
0 conflicts
0x0e6a4aaf…aca5
0x065c9d…c394
2 touches
0 conflicts
0x27e99a9f…2e5f
0x065c9d…c394
2 touches
0 conflicts
0x6f08361d…bda6
0x065c9d…c394
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 0xb06c5ce446…ec99c7
Audit this contract →
← previous block·next block →recent activity