pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,215,367
27 transactions · 19 stateful · 2026-05-13 00:50:32 UTC
Parallelism
81/100
Blocked
37%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,215,367 · 27 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
2w05w06w111w117w018w019w120w221w322w426w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xacefc074…a8bb
0xd32edf…ff58
9 touches
10 conflicts
0x7c403af1…31b1
0x3bd359…433a
4 touches
1 conflict
0x18aed20c…48f3
0x000000…012a
4 touches
1 conflict
0xdd70bea3…1ffe
0x3bd359…433a
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0000
0xd5b70d…615b
4 touches
1 conflict
0x00000000…0002
0xd5b70d…615b
4 touches
1 conflict
0x00000000…0004
0xd5b70d…615b
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: 0xd32edf66…9fff58
10 conflicts on slot 0xacefc074fd…e7a8bb
Audit this contract →
← previous block·next block →recent activity