pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,128,206
← previous block
next block →
recent activity
Analyzing
Block #90,128,206
16 transactions · 11 stateful · 2026-07-25 06:15:18 UTC
Parallelism
94
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,128,206
· 16 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
rz_16jun22_88961909
#2
rz_16jun22_88961909
#3
0x5739cb46
#4
0xccf50a51
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
0x3f5c179b
#8
execFwdPositionOps
#9
execOrders
#10
0x6a6454ed
#11
setData
#12
0xb8024e95
#13
0xb8024e62
#14
execOrders
#15
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x57361451…2eb5
0x350035…7777
2 touches
0 conflicts
0xf4381dd7…e66b
0x350035…7777
2 touches
0 conflicts
0x27216f67…546e
0x3bd359…433a
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x63e48b…53f2
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.
← previous block
·
next block →
recent activity