pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,223,960
12 transactions · 11 stateful · 2026-05-08 10:34:48 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,223,960 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w17w18w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5150abbe…43c3
0x34b655…2a6f
4 touches
1 conflict
0x53c41998…7d52
0x34b655…2a6f
4 touches
1 conflict
0x5aed1bd2…7afa
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xdaca243a…f9de
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0xbd7e37a9…9eb5
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: 0x34b6552d…112a6f
1 conflict on slot 0x5150abbe56…e443c3
Audit this contract →
← previous block·next block →recent activity