pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,856,069
← previous block
next block →
recent activity
Analyzing
Block #92,856,069
13 transactions · 8 stateful · 2026-08-03 19:17:53 UTC
Parallelism
85
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,856,069
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
executePacked
#3
0x50a0b275
#4
0x05ee6a22
#5
0x0c7abd22
#6
0x41a8f47c
#7
execFwdPositionOps
· blocks 1
#8
executeBatch
#10
0x29eed2d3
#11
updateDataFeedsValuesPartial
#12
setData
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c4d9965…6182
0x34b655…2a6f
4 touches
1 conflict
0x6f8644f7…10fa
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x88151b13…c81a
0x065c9d…c394
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x52364236…60a0
0x34b655…2a6f
2 touches
0 conflicts
0xcef70a96…db44
0x34b655…2a6f
2 touches
0 conflicts
0xd22ea5b1…7dcb
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
0x0c4d996568…fb6182
Audit this contract →
← previous block
·
next block →
recent activity