pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#104,703,918
← previous block
next block →
recent activity
Analyzing
Block #104,703,918
17 transactions · 15 stateful · 2026-09-14 08:49:03 UTC
Parallelism
94
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#104,703,918
· 17 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x4ccf0801
#2
matchOrders
#3
0xab083028
#4
0xab083028
#5
execOrder
#6
execOrders
#7
0x5acec890
#8
0x5acec890
#9
0x4cb2db39
#10
0x59558d29
#11
0x59558d29
#12
updatePrices
#13
execFwdPositionOpsV2
#14
0x3f5c179b
#15
execFwdPositionOpsV2
#16
setData
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…004b
0x80c745…7210
2 touches
0 conflicts
0x00000000…004c
0x80c745…7210
2 touches
0 conflicts
0x3bafc3e9…a9ee
0x754704…b603
2 touches
0 conflicts
0x671c83ee…ff09
0x754704…b603
2 touches
0 conflicts
0x9aa1d9bd…baa6
0x754704…b603
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