pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,773,247
← previous block
next block →
recent activity
Analyzing
Block #98,773,247
13 transactions · 12 stateful · 2026-08-24 13:45:37 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,773,247
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
setData
#2
updatePrices
· blocks 1
#4
0x8263f5d9
#5
0x6a8c4b79
#6
0x59558d29
#7
execOrders
#8
handleOps
#9
0x3f5c179b
#10
execFwdPositionOpsV2
#11
execFwdPositionOpsV2
#12
0x6a8c4b79
#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
0xbb3f3c…e046
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x89a4b0a3…2106
0x000000…a032
2 touches
0 conflicts
0xcdf20462…22ec
0x2fd4ee…dfbf
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x54f52f11…1135
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
0x34b655…2a6f
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:
0xbb3f3cb7…74e046
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity