pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,873,176
← previous block
next block →
recent activity
Analyzing
Block #100,873,176
16 transactions · 12 stateful · 2026-08-31 22:18:16 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
#100,873,176
· 16 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x4297b034
#2
updateDataFeedsValuesPartial
#3
0x59558d29
#4
execOrders
#5
execOrders
#6
execOrders
#7
execOrders
#8
executeBatch
#9
setData
#10
execFwdPositionOpsV2
#11
0x5de3085d
#12
execOrders
#13
forward
#14
execFwdPositionOpsV2
#15
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
0xb9cc0d3c…4eb7
0x065c9d…c394
2 touches
0 conflicts
0x0778475b…bd75
0x2a68ba…90c5
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
2 touches
0 conflicts
0x48ed1159…abe9
0x34ae4d…3fc5
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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