pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,567,802
← previous block
next block →
recent activity
Analyzing
Block #95,567,802
8 transactions · 6 stateful · 2026-08-13 07:09:21 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,567,802
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOps
· blocks 2
#3
updateDataFeedsValuesPartial
#4
0x57368ddf
#5
setData
#6
0x59558d29
#2
execFwdPositionOps
· blocks 1
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0c347bfe…4ad0
0x34b655…2a6f
2 touches
0 conflicts
0x124a2fe8…2ea9
0x34b655…2a6f
2 touches
0 conflicts
0x1fcd482b…5ab5
0x34b655…2a6f
2 touches
0 conflicts
0x20af451e…03e1
0x34b655…2a6f
2 touches
0 conflicts
0x20d203c4…5a09
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
0x0f2d78b1bb…5e7363
Audit this contract →
← previous block
·
next block →
recent activity