pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,490,536
16 transactions · 15 stateful · 2026-05-14 07:21:15 UTC
Parallelism
69/100
Blocked
53%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,490,536 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w09w112w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0xffe431af…8faa
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xfdc9ea…8789
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0xedbe6408…924b
0x065c9d…c394
4 touches
1 conflict
0x44ad89ba…cf83
0x23c26b…7777
4 touches
1 conflict
0x81a7ba4d…8c4b
0x23c26b…7777
4 touches
1 conflict
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
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity