pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,379,268
← previous block
next block →
recent activity
Analyzing
Block #102,379,268
17 transactions · 16 stateful · 2026-09-06 04:53:57 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
#102,379,268
· 17 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
matchOrders
#2
0xa96df62f
#3
0xab083028
#4
0xab083028
#5
0x5acec890
#6
0x5acec890
#7
0x5acec890
#8
0x5acec890
#9
0x5acec890
#10
0x59558d29
#11
setData
#12
execFwdPositionOpsV2
#13
0x57368ddf
#14
0x6a9cf1e7
#15
execOrders
#16
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
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x5f72d58f…c445
0x34b655…2a6f
2 touches
0 conflicts
0xdb3937e8…23cb
0x34b655…2a6f
2 touches
0 conflicts
0xf039e2f8…3d8a
0x34b655…2a6f
2 touches
0 conflicts
0xfcdb5918…2b49
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