pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,297,911
← previous block
next block →
recent activity
Analyzing
Block #92,297,911
12 transactions · 7 stateful · 2026-08-01 20:29:13 UTC
Parallelism
83
/100
Blocked
14
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,297,911
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x0c7abd22
#3
0x0c7abd22
#4
handleOps
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
execOrders
#8
setData
· blocks 1
#10
0x59558d29
#11
0xc7e3ec2c
#9
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01344e64…2a46
0x000000…a032
2 touches
0 conflicts
0x177bfe27…a564
0x000000…a032
2 touches
0 conflicts
0x1b714b34…9d4d
0x000000…a032
2 touches
0 conflicts
0x36ac1b6e…54ee
0x000000…a032
2 touches
0 conflicts
0x485a0b0a…ee91
0x000000…a032
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:
0x33176be2…ede078
1 conflict on slot
0x09106a952c…111467
Audit this contract →
← previous block
·
next block →
recent activity