pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,394,450
← previous block
next block →
recent activity
Analyzing
Block #91,394,450
11 transactions · 10 stateful · 2026-07-29 16:43:20 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,394,450
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
execute
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
execOrders
#7
0x6a6a2e20
#8
setData
#10
0x59558d29
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d5e476…8a1f
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x272e5bd6…252d
0x34b655…2a6f
2 touches
0 conflicts
0x356b3459…2e90
0x34b655…2a6f
2 touches
0 conflicts
0x3fefc588…a30e
0x34b655…2a6f
2 touches
0 conflicts
0x495f2eb1…7b0a
0x34b655…2a6f
2 touches
0 conflicts
0x49c03b0b…e048
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.
The bottleneck
Throughput-killer:
Perpl
1 conflict on slot
0x66d5e476c0…268a1f
Audit this contract →
← previous block
·
next block →
recent activity