pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,223,991
43 transactions · 40 stateful · 2026-05-08 10:35:02 UTC
Parallelism
72/100
Blocked
60%
Avg conflicts / tx
1.72
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #73,223,991 · 43 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
1w04w05w06w17w28w013w016w117w018w219w320w422w123w228w629w730w831w932w1033w1134w135w238w339w240w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
16 touches
28 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
12 touches
15 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x0b390c61…dc07
0x065c9d…c394
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xdaca243a…f9de
0x34b655…2a6f
8 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
8 touches
6 conflicts
0x8a35acfb…d1ac
0x8d66a4…3095
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: 0x065c9d28…a9c394
28 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity