pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,839,567
← previous block
next block →
recent activity
Analyzing
Block #75,839,567
10 transactions · 9 stateful · 2026-05-20 13:40:35 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,839,567
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
dagSwapByOrderId
#4
updateDataFeedsValuesPartial
#5
0xbe70473d
#6
setData
#7
redeemDelegations
· blocks 1
#9
0x39435dac
#8
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x2dd412…8319
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x53a21ada…59bb
0x065c9d…c394
2 touches
0 conflicts
0x6653e2fd…a15d
0x065c9d…c394
2 touches
0 conflicts
0x742943dc…cf09
0x065c9d…c394
2 touches
0 conflicts
0xcc4f1f14…aa5f
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:
0x2dd412dd…ac8319
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity