pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,232,425
← previous block
next block →
recent activity
Analyzing
Block #100,232,425
12 transactions · 10 stateful · 2026-08-29 16:30:35 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,232,425
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x5acec890
#4
0x59558d29
#5
0x59558d29
#6
execFwdPositionOpsV2
#7
setData
#8
setData
#9
0x3f5c179b
#10
0x94defb17
· blocks 1
#11
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa387c4a5…5a63
0x8964d7…10f8
4 touches
1 conflict
0xa387c4a5…5a64
0x8964d7…10f8
4 touches
1 conflict
0xa387c4a5…5a66
0x8964d7…10f8
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x6b5f3610…5784
0x8964d7…10f8
4 touches
1 conflict
0x6b5f3610…5785
0x8964d7…10f8
4 touches
1 conflict
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:
0x8964d7c9…5b10f8
1 conflict on slot
0xa387c4a598…525a63
Audit this contract →
← previous block
·
next block →
recent activity