pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,130,686
← previous block
next block →
recent activity
Analyzing
Block #100,130,686
12 transactions · 9 stateful · 2026-08-29 07:58:18 UTC
Parallelism
92
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,130,686
· 12 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0xab083028
#2
0x5acec890
#3
0x928e4afa
#4
updateDataFeedsValuesPartial
#5
0x59558d29
#6
0x0c7abd22
#7
0x0c7abd22
#8
execFwdPositionOpsV2
#9
setData
#10
0xed82b078
#11
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
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x16d77246…bac5
0x34b655…2a6f
2 touches
0 conflicts
0x2a949bb2…8769
0x34b655…2a6f
2 touches
0 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
2 touches
0 conflicts
0x31b6c6dd…59a0
0x34b655…2a6f
2 touches
0 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
2 touches
0 conflicts
0x395bbb78…0fa0
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