pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,248,025
← previous block
next block →
recent activity
Analyzing
Block #91,248,025
14 transactions · 12 stateful · 2026-07-29 04:25:42 UTC
Parallelism
79
/100
Blocked
17
%
Avg conflicts / tx
0.21
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,248,025
· 14 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
· blocks 2
#4
execute
#5
0x3f5c179b
#6
0x3f5c179b
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
forward
#10
execFwdPositionOps
#11
updateDataFeedsValuesPartial
#12
0x6a69813e
#13
setData
#2
updatePrices
· blocks 1
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
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
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x6676e87f…b88f
0x2a68ba…90c5
2 touches
0 conflicts
0xdaf4f143…58d4
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…003d
0x447d2e…e9f5
2 touches
0 conflicts
0x07de41c2…6056
0x447d2e…e9f5
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