pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,201,849
62 transactions · 52 stateful · 2026-05-08 08:07:41 UTC
Parallelism
84/100
Blocked
69%
Avg conflicts / tx
1.81
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,201,849 · 62 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w17w08w110w111w012w013w114w215w318w220w323w424w225w226w143w354w155w256w357w458w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
20 touches
45 conflicts
0xe6455d1f…1029
0x754704…b603
12 touches
15 conflicts
0x0d0b2509…074d
0x3bd359…433a
12 touches
15 conflicts
0x8d143207…a141
0xd32edf…ff58
11 touches
15 conflicts
0x0d622e34…0000
0x681e90…ae09
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0xdfda089f…747f
0x3bd359…433a
8 touches
6 conflicts
0x7f189cf6…afab
0x065c9d…c394
8 touches
6 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: 0xab35264b…1cfa38
45 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity