pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,491,862
← previous block
next block →
recent activity
Analyzing
Block #74,491,862
8 transactions · 8 stateful · 2026-05-14 07:30:06 UTC
Parallelism
63
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,491,862
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x9e76c652
#2
updateDataFeedsValuesPartial
#3
setData
#4
redeemDelegations
#5
0x39435dac
· blocks 1
#6
0x39435dac
· blocks 1
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb138d087…4689
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0006
0x2ab50b…5c41
2 touches
0 conflicts
0x05b8ccbb…46bc
0x2ab50b…5c41
2 touches
0 conflicts
0x06d60e39…4ebd
0x2ab50b…5c41
2 touches
0 conflicts
0x0ae154fb…778b
0x2ab50b…5c41
2 touches
0 conflicts
0x0eff4754…f974
0x2ab50b…5c41
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
0xb138d08737…2b4689
Audit this contract →
← previous block
·
next block →
recent activity