pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,190,673
80 transactions · 45 stateful · 2026-05-12 22:06:17 UTC
Parallelism
76/100
Blocked
67%
Avg conflicts / tx
2.54
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #74,190,673 · 80 txs across 19 waves · depth 19
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
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w19w110w211w215w026w031w232w336w137w238w339w440w541w642w749w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6235697…00a5
0xd32edf…ff58
37 touches
171 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x56a919c4…ab49
0xee8c0e…1242
8 touches
6 conflicts
0x2a354a63…0515
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
6 touches
3 conflicts
0x12309510…0ac2
0x000000…012a
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
171 conflicts on slot 0xa62356970b…be00a5
Audit this contract →
← previous block·next block →recent activity