pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,696,091
37 transactions · 27 stateful · 2026-05-10 15:02:03 UTC
Parallelism
78/100
Blocked
59%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,696,091 · 37 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w07w112w016w017w118w219w320w421w522w123w224w325w426w527w628w129w736w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ea0c740…aade
0xd32edf…ff58
15 touches
28 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0xc6417de0…2191
0xc8689a…ee79
8 touches
6 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
8 touches
6 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
6 touches
3 conflicts
0x2c5e8e5f…769b
0x34b655…2a6f
6 touches
3 conflicts
0x3e733ae4…4598
0x34b655…2a6f
6 touches
3 conflicts
0x1319ae2c…7f9a
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0x5ea0c74099…04aade
Audit this contract →
← previous block·next block →recent activity