pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,285,936
70 transactions · 48 stateful · 2026-05-04 02:26:44 UTC
Parallelism
77/100
Blocked
71%
Avg conflicts / tx
2.19
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #72,285,936 · 70 txs across 16 waves · depth 16
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
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w09w011w120w223w324w325w226w127w428w029w132w033w134w235w345w547w354w456w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbad68552…e6bf
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0xea02471d…1542
0x34b655…2a6f
14 touches
21 conflicts
0x3254d19b…f714
0x34b655…2a6f
12 touches
15 conflicts
0x65e795ca…0320
0x34b655…2a6f
12 touches
15 conflicts
0x8aa1941d…2988
0x34b655…2a6f
12 touches
15 conflicts
0x35b65947…44d1
0xc8689a…ee79
12 touches
15 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
45 conflicts on slot 0xbad6855239…f0e6bf
Audit this contract →
← previous block·next block →recent activity