pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,560,462
← previous block
next block →
recent activity
Analyzing
Block #100,560,462
13 transactions · 13 stateful · 2026-08-30 20:04:48 UTC
Parallelism
77
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,560,462
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xa96df62f
#2
0xab083028
#3
0xa96df62f
#4
matchOrders
#5
0x5acec890
#6
updateDataFeedsValuesPartial
#7
execOrders
· blocks 1
#8
execOrders
#11
0x6a948d57
#12
setData
#9
execFwdPositionOpsV2
· blocks 1
#10
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
9
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x733c7779…a647
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x00532bf5…5711
0x754704…b603
2 touches
0 conflicts
0x0eff0903…8165
0x754704…b603
2 touches
0 conflicts
0xe9e92bac…00ed
0x754704…b603
2 touches
0 conflicts
0x68c08dd2…be14
0x99c7a7…8bf0
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
0x733c7779fd…f4a647
Audit this contract →
← previous block
·
next block →
recent activity