pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,331,232
← previous block
next block →
recent activity
Analyzing
Block #74,331,232
10 transactions · 8 stateful · 2026-05-13 13:41:06 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
#74,331,232
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe2dc7dc3
· blocks 1
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
redeemDelegations
#6
forward
#7
forward
#8
setData
#9
0xf06c5e…0321
#2
0x1a945f9c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x455b104f…3960
0xea1b8e…c5ec
4 touches
1 conflict
0xbc33a929…8b24
0xea1b8e…c5ec
4 touches
1 conflict
0xd8eb2d31…2ac0
0xea1b8e…c5ec
4 touches
1 conflict
0xeef70cb9…5de7
0xea1b8e…c5ec
4 touches
1 conflict
0x493bc17c…2318
0x1efe02…37d6
2 touches
0 conflicts
0xa49f9e98…a1b2
0x1efe02…37d6
2 touches
0 conflicts
0xa67b76d8…97ff
0x1efe02…37d6
2 touches
0 conflicts
0x749437cf…2fc0
0x2880ab…7b43
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:
0xea1b8e4a…8fc5ec
1 conflict on slot
0x455b104f81…2e3960
Audit this contract →
← previous block
·
next block →
recent activity