pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,616,397
← previous block
next block →
recent activity
Analyzing
Block #99,616,397
14 transactions · 12 stateful · 2026-08-27 12:41:47 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,616,397
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updatePrices
· blocks 1
#4
updatePrices
#5
0x928e4afa
#6
0x6a903102
#7
0x59558d29
#8
bet
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#11
updateTemporalNumericValuesV1
#12
setData
#13
execOrders
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 conflicts
0x5e0b8bbe…377b
0x34b655…2a6f
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x2a07e64e…fe77
0x754704…b603
2 touches
0 conflicts
0x3167dcb2…f7f7
0x754704…b603
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:
0xf5b5f7f8…a36d70
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity