pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,613,076
55 transactions · 37 stateful · 2026-05-14 21:04:29 UTC
Parallelism
84/100
Blocked
59%
Avg conflicts / tx
1.42
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #74,613,076 · 55 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w07w18w110w012w013w114w016w217w122w323w235w236w337w438w539w642w744w847w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42513dba…cf12
0xd32edf…ff58
17 touches
36 conflicts
0xadac4a86…c2bc
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x6af306bb…2e81
0x3bd359…433a
8 touches
6 conflicts
0xffe431af…8faa
0x065c9d…c394
8 touches
6 conflicts
0xce8bbe33…b72e
0x3bd359…433a
8 touches
6 conflicts
0x00000000…003d
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: 0xd32edf66…9fff58
36 conflicts on slot 0x42513dba18…35cf12
Audit this contract →
← previous block·next block →recent activity