pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,283,745
45 transactions · 33 stateful · 2026-05-04 02:11:58 UTC
Parallelism
67/100
Blocked
70%
Avg conflicts / tx
2.71
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #72,283,745 · 45 txs across 15 waves · depth 15
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
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w29w010w013w014w115w216w317w322w423w524w625w726w127w828w929w1030w1132w233w336w437w139w1243w1344w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79d76741…7f67
0xd32edf…ff58
29 touches
105 conflicts
0x00000000…0004
0x63e48b…53f2
8 touches
6 conflicts
0x9a555477…19a8
0x754704…b603
8 touches
6 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0000
0x63e48b…53f2
8 touches
6 conflicts
0x00000000…0003
0x63e48b…53f2
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x24968e6d…0132
0x065c9d…c394
6 touches
3 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
105 conflicts on slot 0x79d76741c8…347f67
Audit this contract →
← previous block·next block →recent activity