pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,409,595
41 transactions · 38 stateful · 2026-05-13 22:22:35 UTC
Parallelism
63/100
Blocked
76%
Avg conflicts / tx
3.39
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #74,409,595 · 41 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w07w18w29w310w411w512w613w714w815w916w1017w1118w1219w1320w1421w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
30 touches
105 conflicts
0x00000000…0002
0x019883…2a9a
10 touches
10 conflicts
0x44ad89ba…cf83
0x0cc9b2…7777
10 touches
10 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
10 touches
10 conflicts
0x00000000…0000
0x019883…2a9a
10 touches
10 conflicts
0x1c389468…6b0e
0x34b655…2a6f
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0xa10c86f8…4b74
0x3bd359…433a
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: 0xab35264b…1cfa38
105 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity