pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,160,480
← previous block
next block →
recent activity
Analyzing
Block #100,160,480
15 transactions · 8 stateful · 2026-08-29 10:28:26 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
#100,160,480
· 15 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
updatePrices
#2
0x8263f5d9
#3
execOrders
#4
0x5acec890
#5
0x59558d29
#6
0x0c7abd22
#7
0x0c7abd22
#8
0x0c7abd22
#9
0x0c7abd22
#10
0x0c7abd22
#11
0x0c7abd22
#12
execFwdPositionOpsV2
#13
setData
#14
0x6a92b4c2
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
0x15698ac9…2a46
0x34b655…2a6f
2 touches
0 conflicts
0x258fcaf5…2084
0x34b655…2a6f
2 touches
0 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
2 touches
0 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
2 touches
0 conflicts
0x9b36f19f…fa5a
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