pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,903,097
← previous block
next block →
recent activity
Analyzing
Block #75,903,097
14 transactions · 9 stateful · 2026-05-20 20:44:42 UTC
Parallelism
86
/100
Blocked
11
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,903,097
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
revealWithCallback
#2
updatePrices
· blocks 1
#4
0x982f27…7d1d
#5
0x5bf9264c
#6
0x5bf9264c
#7
updateDataFeedsValuesPartial
#8
0x0f6795d9
#9
0x0f6795d9
#10
0x5339c59f
#11
0xed82b078
#12
setData
#13
0x39435dac
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x19c959f1…5341
0x065c9d…c394
2 touches
0 conflicts
0x3170a930…2681
0x34b655…2a6f
2 touches
0 conflicts
0x3732c6c9…ded6
0x34b655…2a6f
2 touches
0 conflicts
0x5c7e03cf…13a1
0x34b655…2a6f
2 touches
0 conflicts
0x699e5877…05ab
0x34b655…2a6f
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:
0xab35264b…1cfa38
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity