pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,979,424
21 transactions · 18 stateful · 2026-05-11 22:38:52 UTC
Parallelism
43/100
Blocked
67%
Avg conflicts / tx
3.19
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #73,979,424 · 21 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
3w04w15w26w37w48w59w610w711w812w913w1014w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0003
0xfdc9ea…8789
24 touches
66 conflicts
0x81a7ba4d…8c4b
0x23c26b…7777
24 touches
66 conflicts
0x08fdca0b…4abf
0x3bd359…433a
24 touches
66 conflicts
0x00000000…0000
0xfdc9ea…8789
24 touches
66 conflicts
0x00000000…0001
0xfdc9ea…8789
24 touches
66 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xef890d56…d1d5
0x065c9d…c394
3 touches
1 conflict
0xe2e1cd37…914f
0x065c9d…c394
3 touches
1 conflict
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: 0xfdc9ea59…b68789
66 conflicts on slot 0x0000000000…000003
Audit this contract →
← previous block·next block →recent activity