pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,638,379
27 transactions · 18 stateful · 2026-05-14 23:53:12 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,638,379 · 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
1w02w14w25w36w49w321w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed2c30dc…99c1
0xd32edf…ff58
9 touches
10 conflicts
0x4dd1db39…a996
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
0x17a7f697…dcb8
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 0xed2c30dc62…e099c1
Audit this contract →
← previous block·next block →recent activity