pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,051,682
← previous block
next block →
recent activity
Analyzing
Block #102,051,682
15 transactions · 14 stateful · 2026-09-05 01:13:44 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
#102,051,682
· 15 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
executePacked
#2
execOrders
#3
0xab083028
#4
0xab083028
#5
0x5acec890
#6
0x5acec890
#7
0x5acec890
#8
0x59558d29
#9
0xbb1740dd
#10
setData
#11
execFwdPositionOpsV2
#12
execFwdPositionOpsV2
#13
0x6a9b6ccb
#14
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
0x0246d82c…6ade
0x065c9d…c394
2 touches
0 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
2 touches
0 conflicts
0x4f3cc09a…2804
0x34b655…2a6f
2 touches
0 conflicts
0x64dc8f6e…a0be
0x34b655…2a6f
2 touches
0 conflicts
0x65f011a5…bc6e
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