pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,626,054
62 transactions · 44 stateful · 2026-05-14 22:31:06 UTC
Parallelism
81/100
Blocked
64%
Avg conflicts / tx
1.53
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #74,626,054 · 62 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w06w17w213w015w117w318w019w425w526w227w639w745w546w648w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb44af574…041d
0xd32edf…ff58
17 touches
36 conflicts
0x17606ba6…1b6e
0x754704…b603
12 touches
15 conflicts
0xffe431af…8faa
0x065c9d…c394
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7cf3eb0f…06c5
0x34b655…2a6f
8 touches
6 conflicts
0xa92c8763…6d7f
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xef184a54…5801
0x34b655…2a6f
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: 0xd32edf66…9fff58
36 conflicts on slot 0xb44af57497…4f041d
Audit this contract →
← previous block·next block →recent activity