pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,607,806
← previous block
next block →
recent activity
Analyzing
Block #99,607,806
14 transactions · 13 stateful · 2026-08-27 11:57:31 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,607,806
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
supply
#2
matchOrders
#3
0x5acec890
#4
0x59558d29
#5
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
#8
executeBatch
#9
0x3f5c179b
#10
0x3f5c179b
#11
setData
#12
execOrders
#13
execOrders
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x101be604…5db0
0x34b655…2a6f
4 touches
1 conflict
0x04994ed2…9032
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x8f478f26…9d56
0x000000…012a
2 touches
0 conflicts
0x9cfe0a4d…1f95
0x000000…012a
2 touches
0 conflicts
0x9d120070…8aff
0x57ea24…2cec
2 touches
0 conflicts
0xe60cff44…1b50
0x57ea24…2cec
2 touches
0 conflicts
0x53fa77e0…0d4f
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
0x101be6046a…c75db0
Audit this contract →
← previous block
·
next block →
recent activity