pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,680,782
46 transactions · 34 stateful · 2026-05-10 13:18:57 UTC
Parallelism
74/100
Blocked
76%
Avg conflicts / tx
1.8
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #73,680,782 · 46 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
1w02w13w24w35w06w410w227w528w631w532w633w734w835w936w1037w1139w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0x529acb6a…fcc6
0x065c9d…c394
12 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
12 touches
15 conflicts
0x0ac31945…2c72
0x065c9d…c394
10 touches
10 conflicts
0x3e733ae4…4598
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x157b6348…8604
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 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: 0x065c9d28…a9c394
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity