pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,529,293
← previous block
next block →
recent activity
Analyzing
Block #95,529,293
8 transactions · 6 stateful · 2026-08-13 03:55:40 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,529,293
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
updateDataFeedsValuesPartial
#4
forward
#5
setData
#6
0x17bb45…50fc
#7
0x59558d29
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x1a5d321d…a474
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x10797f0b…439a
0x34b655…2a6f
2 touches
0 conflicts
0x12659c8c…062e
0x34b655…2a6f
2 touches
0 conflicts
0x19489614…582d
0x34b655…2a6f
2 touches
0 conflicts
0x2697123c…8526
0x34b655…2a6f
2 touches
0 conflicts
0x5770813f…1aa7
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
0xe5bb3628b5…71e5f1
Audit this contract →
← previous block
·
next block →
recent activity