pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,723,229
← previous block
next block →
recent activity
Analyzing
Block #98,723,229
14 transactions · 13 stateful · 2026-08-24 09:33:52 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,723,229
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x41a8f47c
#2
execOrders
#3
0x59558d29
#4
execFwdPositionOpsV2
#5
matchOrders
#6
execFwdPositionOpsV2
· blocks 1
#7
forward
#8
bet
#9
0xed82b078
#10
updateDataFeedsValuesPartial
#11
setData
#12
execOrders
· blocks 1
#13
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
12
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x10a81eed…c249
0x340143…768f
2 touches
0 conflicts
0x5d601639…d720
0x340143…768f
2 touches
0 conflicts
0x26d48e6a…2706
0x40c49f…2af0
2 touches
0 conflicts
0x0b552eae…fbd9
0x754704…b603
2 touches
0 conflicts
0x4e858410…6ba5
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:
Perpl
1 conflict on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity