pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,872,053
← previous block
next block →
recent activity
Analyzing
Block #99,872,053
13 transactions · 13 stateful · 2026-08-28 10:15:41 UTC
Parallelism
85
/100
Blocked
15
%
Avg conflicts / tx
0.23
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,872,053
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0xab083028
#4
0x5acec890
#5
0x59558d29
#6
execOrders
· blocks 1
#7
execFwdPositionOpsV2
· blocks 1
#8
executeBatch
#10
forward
#11
transferWithAuthorization
#12
setData
#2
matchOrders
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
7
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfac3ce0…6699
0x99c7a7…8bf0
4 touches
1 conflict
0x1e602875…e2a7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xbfb4b02a…4b47
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00532bf5…5711
0x754704…b603
4 touches
1 conflict
0x0eff0903…8165
0x754704…b603
4 touches
1 conflict
0x777c9106…162a
0x754704…b603
4 touches
1 conflict
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
0xdfac3ce097…826699
Audit this contract →
← previous block
·
next block →
recent activity