pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,462,405
19 transactions · 6 stateful · 2026-05-14 04:14:07 UTC
Parallelism
89/100
Blocked
33%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,462,405 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33018431…8f5c
0x188d58…ea8e
4 touches
1 conflict
0x33018431…8f5e
0x188d58…ea8e
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x4aa4f53b…899f
0x188d58…ea8e
4 touches
1 conflict
0x0d55f5cc…94f7
0xd32edf…ff58
3 touches
1 conflict
0x3b99eb5d…2c09
0x188d58…ea8e
2 touches
0 conflicts
0x4aa4f53b…89a0
0x188d58…ea8e
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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: 0x188d586d…f9ea8e
1 conflict on slot 0x330184318b…418f5c
Audit this contract →
← previous block·next block →recent activity