pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,741,752
44 transactions · 28 stateful · 2026-05-01 13:56:24 UTC
Parallelism
73/100
Blocked
61%
Avg conflicts / tx
1.86
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #71,741,752 · 44 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
1w06w08w013w015w116w017w018w119w225w127w228w330w431w532w233w634w735w137w838w939w1043w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b363413…228c
0xd32edf…ff58
23 touches
66 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
8 touches
6 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0002
0x7e9d3a…9fda
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xe8327bf4…bd19
0x065c9d…c394
5 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: 0xd32edf66…9fff58
66 conflicts on slot 0x1b36341370…fc228c
Audit this contract →
← previous block·next block →recent activity