pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,919,635
← previous block
next block →
recent activity
Analyzing
Block #75,919,635
10 transactions · 10 stateful · 2026-05-20 22:34:46 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,919,635
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
redeemDelegations
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
swap
#5
0x98717539
· blocks 1
#6
collect
#7
setData
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x502bbd53…fd54
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x846f2172…fd54
0x0555e3…2b9c
2 touches
0 conflicts
0x9bad8822…a28c
0x0555e3…2b9c
2 touches
0 conflicts
0xe64f78af…51a7
0x0555e3…2b9c
2 touches
0 conflicts
0x892daf6e…48d8
0x065c9d…c394
2 touches
0 conflicts
0xa81c4269…3977
0x065c9d…c394
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:
Perpl
1 conflict on slot
0x502bbd53dc…eefd54
Audit this contract →
← previous block
·
next block →
recent activity