pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,510,511
← previous block
next block →
recent activity
Analyzing
Block #74,510,511
13 transactions · 11 stateful · 2026-05-14 09:34:55 UTC
Parallelism
77
/100
Blocked
18
%
Avg conflicts / tx
0.15
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,510,511
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
removeLiquidity
#2
updateDataFeedsValuesPartial
#3
0x5bf9264c
#4
0x98717539
#5
claimRewards
#6
0x6a0597b7
#7
setData
#8
redeemDelegations
#9
0x39435dac
· blocks 1
#12
jMMeC
#10
0x39435dac
· blocks 1
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
11
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe20cb8f…f03d
0x34b655…2a6f
4 touches
1 conflict
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x51799ba4…ac79
0x5afd3e…7620
2 touches
0 conflicts
0x55dcb0fd…3030
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
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
0xfe20cb8f2c…3ef03d
Audit this contract →
← previous block
·
next block →
recent activity