pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,496,436
21 transactions · 19 stateful · 2026-05-05 01:49:32 UTC
Parallelism
81/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,496,436 · 21 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
1w02w13w25w011w112w013w114w315w016w118w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9250fc01…f07d
0xd32edf…ff58
7 touches
6 conflicts
0xffe431af…8faa
0x065c9d…c394
6 touches
3 conflicts
0xf3981be5…2c47
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x2ce2d49e…d189
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 0x9250fc0126…caf07d
Audit this contract →
← previous block·next block →recent activity