pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,353,339
45 transactions · 35 stateful · 2026-05-09 00:55:33 UTC
Parallelism
78/100
Blocked
63%
Avg conflicts / tx
0.87
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,353,339 · 45 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w110w011w112w213w314w415w416w217w418w421w022w123w226w029w530w635w736w844w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d87512b…897c
0x065c9d…c394
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0xb4ec6576…44ff
0xd32edf…ff58
7 touches
6 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
6 touches
3 conflicts
0x8d0dfe2c…3345
0x2a68ba…90c5
6 touches
3 conflicts
0x12309510…0ac2
0x000000…012a
6 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
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
10 conflicts on slot 0x4d87512b00…43897c
Audit this contract →
← previous block·next block →recent activity