pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,478,947
44 transactions · 31 stateful · 2026-05-18 21:27:58 UTC
Parallelism
68/100
Blocked
74%
Avg conflicts / tx
2.55
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #75,478,947 · 44 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w610w711w812w215w216w317w831w932w1040w1141w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2de35673…4fce
0xd32edf…ff58
21 touches
55 conflicts
0x17606ba6…1b6e
0x754704…b603
16 touches
28 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
10 touches
10 conflicts
0xe75ce681…ba61
0x188d58…ea8e
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0018
0x1b6862…e19c
10 touches
10 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: 0xd32edf66…9fff58
55 conflicts on slot 0x2de356733b…584fce
Audit this contract →
← previous block·next block →recent activity