pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,478,943
48 transactions · 29 stateful · 2026-05-18 21:27:57 UTC
Parallelism
67/100
Blocked
72%
Avg conflicts / tx
2.21
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #75,478,943 · 48 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w47w59w612w714w716w820w922w1025w1131w1232w1335w1338w1442w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
24 touches
66 conflicts
0xee0a9ebb…c425
0x0555e3…2b9c
14 touches
21 conflicts
0x00000000…0000
0x9b60e5…f8ac
14 touches
21 conflicts
0x5dfa485c…cf52
0x754704…b603
14 touches
21 conflicts
0xab45b4a4…0a99
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0004
0x9b60e5…f8ac
12 touches
15 conflicts
0x93afca4c…b478
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 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: 0x754704bc…afb603
66 conflicts on slot 0x17606ba612…ea1b6e
Audit this contract →
← previous block·next block →recent activity