pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,976,965
← previous block
next block →
recent activity
Analyzing
Block #91,976,965
14 transactions · 14 stateful · 2026-07-31 17:35:04 UTC
Parallelism
86
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,976,965
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
#3
updatePrices
· blocks 1
#5
updateDataFeedsValuesPartial
#6
forward
#7
execFwdPositionOps
#8
forward
#9
execFwdPositionOps
#10
0x6a6cdd40
#11
proposeResolution
#12
execOrders
#13
0x59558d29
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x91855e…ac7e
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x21898044…a071
0x065c9d…c394
2 touches
0 conflicts
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x560c0736…6e74
0x065c9d…c394
2 touches
0 conflicts
0x90d2a27a…bdd4
0x065c9d…c394
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:
0x91855e79…58ac7e
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity