pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,539,874
← previous block
next block →
recent activity
Analyzing
Block #95,539,874
11 transactions · 10 stateful · 2026-08-13 04:48:54 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,539,874
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 2
#2
0x5acec890
#3
execFwdPositionOps
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#8
0x260595cf
#9
setData
#10
0x59558d29
#4
execFwdPositionOps
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fe1e6e0…f553
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0a57a2b8…3cdd
0x34b655…2a6f
4 touches
1 conflict
0x5a08ca7f…6546
0x34b655…2a6f
4 touches
1 conflict
0x8b501dcf…1040
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa779293b…5e59
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0001
0x000000…1000
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
0x0fe1e6e0ec…9df553
Audit this contract →
← previous block
·
next block →
recent activity