pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,283,145
39 transactions · 34 stateful · 2026-05-04 02:07:56 UTC
Parallelism
82/100
Blocked
62%
Avg conflicts / tx
1.28
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #72,283,145 · 39 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w28w09w010w011w113w314w416w221w022w123w224w125w226w329w430w435w336w437w538w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbad68552…e6bf
0x34b655…2a6f
14 touches
21 conflicts
0x3d666060…052f
0xd32edf…ff58
9 touches
10 conflicts
0x24968e6d…0132
0x065c9d…c394
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xdfda089f…747f
0x3bd359…433a
8 touches
6 conflicts
0x2877f440…c2c8
0x34b655…2a6f
6 touches
3 conflicts
0x3254d19b…f714
0x34b655…2a6f
6 touches
3 conflicts
0x414e9446…4b59
0x34b655…2a6f
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: 0x34b6552d…112a6f
21 conflicts on slot 0xbad6855239…f0e6bf
Audit this contract →
← previous block·next block →recent activity