pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,696,528
← previous block
next block →
recent activity
Analyzing
Block #92,696,528
11 transactions · 10 stateful · 2026-08-03 05:54:55 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
#92,696,528
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x5acec890
#3
0xb2d4797b
#4
0x3f5c179b
#5
executeBatch
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
setData
#9
0x59558d29
· blocks 1
#10
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x1ad59947…dd02
0x34b655…2a6f
2 touches
0 conflicts
0x1fc96968…a760
0x34b655…2a6f
2 touches
0 conflicts
0x241ca014…4529
0x34b655…2a6f
2 touches
0 conflicts
0x2a0c0a9c…5ea2
0x34b655…2a6f
2 touches
0 conflicts
0x2ace2029…e9ad
0x34b655…2a6f
2 touches
0 conflicts
0x3a5d6372…34cd
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:
0x80c74517…647210
1 conflict on slot
0x0000000000…00004b
Audit this contract →
← previous block
·
next block →
recent activity