pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,160,937
← previous block
next block →
recent activity
Analyzing
Block #99,160,937
13 transactions · 12 stateful · 2026-08-25 22:23:03 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
#99,160,937
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0xab083028
#3
execOrders
· blocks 1
#5
0x59558d29
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
updateDataFeedsValuesPartial
#9
allocate
#10
relay
#11
setData
#12
execOrders
#4
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fc6ea79…e2dc
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x5e91cb84…8fa3
0x065c9d…c394
2 touches
0 conflicts
0xd6f6a7cc…c718
0x065c9d…c394
2 touches
0 conflicts
0xf3d7a307…4d63
0x065c9d…c394
2 touches
0 conflicts
0xf7ee2dd5…b081
0x065c9d…c394
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
0x9fc6ea791d…ace2dc
Audit this contract →
← previous block
·
next block →
recent activity