pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,464,004
← previous block
next block →
recent activity
Analyzing
Block #93,464,004
15 transactions · 14 stateful · 2026-08-05 22:16:38 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
#93,464,004
· 15 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
matchOrders
#2
execOrders
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
executeBatch
#6
permit2TransferAndMulticall
#7
0x94defb17
#8
execFwdPositionOps
#9
updateDataFeedsValuesPartial
#10
0x6a73b6bd
#11
setData
#12
execOrders
#13
0x59558d29
#14
0xc7e3ec2c
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
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x0728ec77…146c
0x34b655…2a6f
2 touches
0 conflicts
0x0db11951…d3e6
0x34b655…2a6f
2 touches
0 conflicts
0x31f6cdda…d22b
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
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