pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,654,805
14 transactions · 14 stateful · 2026-05-10 10:23:34 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,654,805 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w07w28w09w110w211w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfab0decb…7e82
0xd32edf…ff58
7 touches
6 conflicts
0xe6455d1f…1029
0x754704…b603
6 touches
3 conflicts
0x0d0b2509…074d
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x013bb37b…eb4c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
6 conflicts on slot 0xfab0decb17…7c7e82
Audit this contract →
← previous block·next block →recent activity