pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,417,731
← previous block
next block →
recent activity
Analyzing
Block #91,417,731
16 transactions · 15 stateful · 2026-07-29 18:40:51 UTC
Parallelism
81
/100
Blocked
13
%
Avg conflicts / tx
0.19
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,417,731
· 16 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xeabbe9d8
#2
0x6a6a49ab
#3
setData
#4
0x6ad2e98b
#5
0x6a6a49aa
#6
updatePrices
· blocks 2
#9
execFwdPositionOps
#10
0xed82b078
#11
execFwdPositionOps
#12
updateDataFeedsValuesPartial
#13
execOrders
#14
0x59558d29
#15
0xc7e3ec2c
#7
updatePrices
· blocks 1
#8
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0002
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0003
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0004
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0008
0x04ddf6…7f33
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:
0x48cba278…e2b48b
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity