pev.One block, wave by wave
analyticsdocs
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,404,273
31 transactions · 29 stateful · 2026-05-13 21:47:07 UTC
Parallelism
42/100
Blocked
69%
Avg conflicts / tx
5.06
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #74,404,273 · 31 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w1315w1416w1517w1623w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24cfe713…0f91
0x25d593…7777
36 touches
153 conflicts
0xe3ee7f9e…f356
0x3bd359…433a
36 touches
153 conflicts
0x00000000…0003
0x30611e…d8d9
34 touches
136 conflicts
0x00000000…0000
0x30611e…d8d9
34 touches
136 conflicts
0x00000000…0002
0x30611e…d8d9
34 touches
136 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x9ee50340…2f11
0x25d593…7777
2 touches
0 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: 0x25d5934c…297777
153 conflicts on slot 0x24cfe713e3…6c0f91
Audit this contract →
← previous block·next block →recent activity