pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,123,335
← previous block
next block →
recent activity
Analyzing
Block #75,123,335
11 transactions · 10 stateful · 2026-05-17 05:51:31 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,123,335
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
delegate
#2
0xae238fb5
#3
0x1ffa3c9b
· blocks 1
#4
updateDataFeedsValuesPartial
#6
0x5339c59f
#7
0x6a0957da
· blocks 1
#9
setData
#10
0x39435dac
#5
0x5339c59f
#8
0x6a0957da
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x3db35068…c16c
0x065c9d…c394
4 touches
1 conflict
0x55e64298…c81e
0x065c9d…c394
3 touches
1 conflict
0xe0b413fa…d120
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0001
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0b000000…0003
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity