pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,795,895
35 transactions · 30 stateful · 2026-05-11 02:15:35 UTC
Parallelism
63/100
Blocked
70%
Avg conflicts / tx
2.23
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #73,795,895 · 35 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
5w08w09w110w211w312w413w514w615w716w217w318w430w833w1134w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5de96bd3…c60c
0x34b655…2a6f
18 touches
36 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
16 touches
28 conflicts
0xb378025c…30cf
0x34b655…2a6f
16 touches
28 conflicts
0xc6417de0…2191
0xc8689a…ee79
14 touches
21 conflicts
0x313f2565…5b00
0x34b655…2a6f
14 touches
21 conflicts
0xedb848fe…6534
0x34b655…2a6f
14 touches
21 conflicts
0x57de3828…3fbb
0x34b655…2a6f
14 touches
21 conflicts
0xdf7899c0…c53a
0x34b655…2a6f
14 touches
21 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: 0x34b6552d…112a6f
36 conflicts on slot 0x5de96bd34a…ecc60c
Audit this contract →
← previous block·next block →recent activity