pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,255,118
← previous block
next block →
recent activity
Analyzing
Block #99,255,118
14 transactions · 11 stateful · 2026-08-26 06:16:53 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,255,118
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0xab083028
#4
0xab083028
#5
execOrders
#6
execOrders
#7
execOrders
#8
0x59558d29
#9
0xe3a3c9cc
#10
exactInputSingle
#11
execFwdPositionOpsV2
#12
setData
#13
execOrders
#2
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a401109…0866
0x99c7a7…8bf0
4 touches
1 conflict
0xa14b5090…25fc
0x99c7a7…8bf0
4 touches
1 conflict
0x70534dbe…4038
0x754704…b603
4 touches
1 conflict
0xb6238279…83e0
0x754704…b603
4 touches
1 conflict
0xcfedd619…1e91
0x754704…b603
4 touches
1 conflict
0x2d307ea7…8841
0x34b655…2a6f
2 touches
0 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
2 touches
0 conflicts
0x4a538b72…479c
0x34b655…2a6f
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:
0x99c7a72e…c78bf0
1 conflict on slot
0x1a401109d1…040866
Audit this contract →
← previous block
·
next block →
recent activity