pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,359,400
← previous block
next block →
recent activity
Analyzing
Block #74,359,400
9 transactions · 8 stateful · 2026-05-13 16:48:22 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,359,400
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#2
redeemDelegations
#3
0x98717539
· blocks 1
#5
updateDataFeedsValuesPartial
#6
setData
#7
forward
#8
0x6a04abce
#4
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfff38d9f…7063
0x8d66a4…3095
4 touches
1 conflict
0x1b9e654e…0a08
0x34b655…2a6f
4 touches
1 conflict
0x36f4b4f0…0188
0x34b655…2a6f
4 touches
1 conflict
0x5675c293…17d9
0x34b655…2a6f
4 touches
1 conflict
0x5d70606a…1d53
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x62d080e9…4a7c
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
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:
0x8d66a43f…113095
1 conflict on slot
0xfff38d9fe2…647063
Audit this contract →
← previous block
·
next block →
recent activity