pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,796,960
← previous block
next block →
recent activity
Analyzing
Block #75,796,960
10 transactions · 8 stateful · 2026-05-20 08:56:01 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,796,960
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x5bf9264c
· blocks 1
#3
updateDataFeedsValuesPartial
#5
redeemDelegations
#6
0x0f6795d9
#7
setData
#8
0x0f6795d9
#9
0x6a0d7799
#4
0x5bf9264c
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
0x22e0cc1d…ad04
0x34b655…2a6f
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
0x1d99cfbb…a976
0x065c9d…c394
2 touches
0 conflicts
0x52bfeae3…8145
0x065c9d…c394
2 touches
0 conflicts
0x6238d582…a5ce
0x065c9d…c394
2 touches
0 conflicts
0xc0a4237a…10d1
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
0x22e0cc1d4a…90ad04
Audit this contract →
← previous block
·
next block →
recent activity