pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,571,197
47 transactions · 39 stateful · 2026-05-05 10:07:17 UTC
Parallelism
74/100
Blocked
74%
Avg conflicts / tx
2.87
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #72,571,197 · 47 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w18w110w011w112w213w314w415w516w617w718w819w920w1021w1135w239w340w341w442w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x7e9d3a…9fda
24 touches
66 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
20 touches
45 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xbbee74c2…567a
0x065c9d…c394
10 touches
10 conflicts
0xbb1747e2…f78b
0x34b655…2a6f
8 touches
6 conflicts
0x24968e6d…0132
0x065c9d…c394
8 touches
6 conflicts
0x8a35acfb…d1ad
0x8d66a4…3095
8 touches
6 conflicts
0x1b5d2e60…99b5
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: 0x7e9d3a8a…4f9fda
66 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity