pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,284,594
← previous block
next block →
recent activity
Analyzing
Block #99,284,594
10 transactions · 10 stateful · 2026-08-26 08:45:15 UTC
Parallelism
80
/100
Blocked
30
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,284,594
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0x59558d29
#3
execFwdPositionOpsV2
· blocks 2
#6
0x3f5c179b
#7
setData
#8
0x61d59c2d
· blocks 1
#4
execFwdPositionOpsV2
#5
execFwdPositionOpsV2
#9
swapExactTokensForTokens
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0x0fd2cbc5…476b
0x77d53b…8080
4 touches
1 conflict
0x85c42e7e…1a06
0x77d53b…8080
4 touches
1 conflict
0xe3abe489…ebf2
0x77d53b…8080
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x15c6ded9…48e7
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
0xbd590df7f7…cf9891
Audit this contract →
← previous block
·
next block →
recent activity