pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,027,813
← previous block
next block →
recent activity
Analyzing
Block #100,027,813
14 transactions · 10 stateful · 2026-08-28 23:20:23 UTC
Parallelism
93
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,027,813
· 14 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execute_route
#2
matchOrders
#3
0xab083028
#4
0x928e4afa
#5
setData
#6
0x59558d29
#7
execOrders
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#11
execOrders
#12
0x6a92182f
#13
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x044844a0…7418
0x34b655…2a6f
2 touches
0 conflicts
0x3b3642d0…3ef0
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 conflicts
0x58620f29…db5a
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.
← previous block
·
next block →
recent activity