pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,365,908
32 transactions · 28 stateful · 2026-05-04 11:19:59 UTC
Parallelism
84/100
Blocked
57%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #72,365,908 · 32 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
1w03w04w05w06w17w18w113w014w115w016w117w118w219w320w421w123w224w226w329w230w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee1ea58e…330b
0xd32edf…ff58
9 touches
10 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
8 touches
6 conflicts
0xadac4a86…c2bc
0x34b655…2a6f
8 touches
6 conflicts
0xf3981be5…2c47
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xffe431af…8faa
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
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 0xee1ea58e43…f5330b
Audit this contract →
← previous block·next block →recent activity