pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,525,786
74 transactions · 37 stateful · 2026-05-19 02:49:06 UTC
Parallelism
82/100
Blocked
70%
Avg conflicts / tx
1.38
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #75,525,786 · 74 txs across 13 waves · depth 13
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
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w09w110w123w227w237w339w042w143w044w447w150w251w352w454w555w656w758w360w273w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63da7859…8b8c
0xd32edf…ff58
25 touches
78 conflicts
0x00000000…0004
0x63e48b…53f2
8 touches
6 conflicts
0x9a555477…19a8
0x754704…b603
8 touches
6 conflicts
0x00000000…0000
0x63e48b…53f2
8 touches
6 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
8 touches
6 conflicts
0x56a919c4…ab49
0xee8c0e…1242
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5086c64a…28ba
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: 0xd32edf66…9fff58
78 conflicts on slot 0x63da785984…3c8b8c
Audit this contract →
← previous block·next block →recent activity