pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,516,213
← previous block
next block →
recent activity
Analyzing
Block #75,516,213
13 transactions · 10 stateful · 2026-05-19 01:43:37 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,516,213
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
execute
· blocks 1
#3
placeBet
#5
0xe7be4706
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
updatePriceFeedsIfNecessary
#9
forward
#10
0xed82b078
#11
0x6a0bc0c1
#12
setData
#4
0xe7be4706
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x846f2172…fd54
0x0555e3…2b9c
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x62e20208…be65
0x0555e3…2b9c
2 touches
0 conflicts
0x9c11d943…f33a
0x0555e3…2b9c
2 touches
0 conflicts
0x00000000…0000
0x094452…0a09
2 touches
0 conflicts
0x00000000…0002
0x094452…0a09
2 touches
0 conflicts
0x46cb45de…a566
0x188d58…ea8e
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:
Wrapped BTC (WBTC)
1 conflict on slot
0x846f21722e…fdfd54
Audit this contract →
← previous block
·
next block →
recent activity