pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,796,003
← previous block
next block →
recent activity
Analyzing
Block #74,796,003
14 transactions · 12 stateful · 2026-05-15 17:25:49 UTC
Parallelism
86
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,796,003
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
redeemDelegations
· blocks 1
#3
0x98717539
#4
forward
· blocks 1
#5
forward
#6
forward
#7
forward
#9
0xed82b078
#10
updateDataFeedsValuesPartial
#11
updateDataFeedsValuesPartial
#12
0x6a075795
#13
setData
#2
redeemDelegations
#8
forward
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x465ae8…cc5a
4 touches
1 conflict
0x00000000…000b
0xd3f273…09af
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0b28bf77…e53a
0x34b655…2a6f
2 touches
0 conflicts
0x32ee90db…decc
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0xac8e97a0…8426
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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:
0x465ae8f3…c1cc5a
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity