pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,218,313
23 transactions · 17 stateful · 2026-05-13 01:10:10 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,218,313 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w19w010w113w014w215w316w417w521w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388b8cd0…ad18
0xd32edf…ff58
9 touches
10 conflicts
0x46cb45de…a566
0x188d58…ea8e
4 touches
1 conflict
0x46cb45de…a568
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
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 0x388b8cd099…27ad18
Audit this contract →
← previous block·next block →recent activity