pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,288,962
← previous block
next block →
recent activity
Analyzing
Block #94,288,962
9 transactions · 7 stateful · 2026-08-08 19:31:56 UTC
Parallelism
67
/100
Blocked
43
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,288,962
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOps
· blocks 2
#3
updateDataFeedsValuesPartial
#4
placeAndExecuteMarketSell
· blocks 1
#7
0xed82b078
#8
setData
#2
execFwdPositionOps
· blocks 1
#5
batchUpdate
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x20dd3281…1a00
0xa6afd3…d132
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x187bb168…d783
0x34b655…2a6f
2 touches
0 conflicts
0x21ef0807…d889
0x34b655…2a6f
2 touches
0 conflicts
0x324d7370…8b59
0x34b655…2a6f
2 touches
0 conflicts
0x324d7370…8b5a
0x34b655…2a6f
2 touches
0 conflicts
0x4e135144…4167
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
3 conflicts on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity