pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,292,867
← previous block
next block →
recent activity
Analyzing
Block #94,292,867
8 transactions · 5 stateful · 2026-08-08 19:51:41 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,292,867
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#4
updateDataFeedsValuesPartial
#5
verifyOracleProofV2
#7
setData
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26ea8b6f…d6fc
0x34b655…2a6f
4 touches
1 conflict
0x1f90c45d…89c2
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xebc963ef…7eae
0x34b655…2a6f
4 touches
1 conflict
0x9a09cf4e…f19f
0x34b655…2a6f
4 touches
1 conflict
0x166b18ee…831d
0x34b655…2a6f
2 touches
0 conflicts
0x1d84142d…0d81
0x34b655…2a6f
2 touches
0 conflicts
0x222733a8…8e7a
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
0x26ea8b6f0f…e7d6fc
Audit this contract →
← previous block
·
next block →
recent activity