pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,537,938
← previous block
next block →
recent activity
Analyzing
Block #98,537,938
12 transactions · 11 stateful · 2026-08-23 17:32:57 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,537,938
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updateDataFeedsValuesPartial
#3
0x59558d29
#4
execFwdPositionOpsV2
· blocks 1
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
0x3f5c179b
#9
0x6a8b2f41
#10
setData
#11
execOrders
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd64af46e…6df1
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x00532bf5…5711
0x754704…b603
2 touches
0 conflicts
0x0eff0903…8165
0x754704…b603
2 touches
0 conflicts
0xe9e92bac…00ed
0x754704…b603
2 touches
0 conflicts
0x00000000…004b
0x80c745…7210
2 touches
0 conflicts
0x00000000…004c
0x80c745…7210
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:
Perpl
1 conflict on slot
0xd64af46ef3…5c6df1
Audit this contract →
← previous block
·
next block →
recent activity