pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,324,490
← previous block
next block →
recent activity
Analyzing
Block #101,324,490
19 transactions · 16 stateful · 2026-09-02 12:09:05 UTC
Parallelism
95
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,324,490
· 19 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
claim
#2
0x0c7abd22
#3
updateDataFeedsValuesPartial
#4
execOrder
#5
execOrder
#6
0x59558d29
#7
0x59558d29
#8
executeBatch
#9
setData
#10
0x94defb17
#11
execFwdPositionOpsV2
#12
execOrders
#13
execOrders
#14
execOrders
#15
execOrders
#16
execOrders
#17
execOrders
#18
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…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001d
0x1b6862…e19c
2 touches
0 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
2 touches
0 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
2 touches
0 conflicts
0x4730fe0c…8960
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