pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,237,285
← previous block
next block →
recent activity
Analyzing
Block #100,237,285
17 transactions · 14 stateful · 2026-08-29 16:55:04 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,237,285
· 17 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execute
#2
exactInputSingle
#3
0x8263f5d9
#4
0x59558d29
#5
0xe3a3c9cc
#6
0x62be7533
#7
0xd62522e3
#8
execFwdPositionOpsV2
#9
setData
#10
execOrders
#11
execOrders
#12
execOrders
#13
execOrders
#14
execOrders
#15
execOrders
#16
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
0x18aed20c…48f3
0x000000…012a
2 touches
0 conflicts
0x4245e4e8…096e
0x000000…012a
2 touches
0 conflicts
0x98f7703d…4dbc
0x065c9d…c394
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
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