pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,399,837
← previous block
next block →
recent activity
Analyzing
Block #74,399,837
9 transactions · 9 stateful · 2026-05-13 21:17:36 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,399,837
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
redeemDelegations
· blocks 1
#4
updateDataFeedsValuesPartial
#5
forward
#6
setData
#7
0x39435dac
· blocks 1
#3
redeemDelegations
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7170c140…36bc
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0xa1f52f…5ce9
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0x62d080e9…4a7c
0x34b655…2a6f
4 touches
1 conflict
0x5138188e…796b
0x34b655…2a6f
2 touches
0 conflicts
0x55b6a001…1e7a
0x34b655…2a6f
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:
0x34b6552d…112a6f
1 conflict on slot
0x7170c140c5…9a36bc
Audit this contract →
← previous block
·
next block →
recent activity