pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,039,873
← previous block
next block →
recent activity
Analyzing
Block #88,039,873
11 transactions · 9 stateful · 2026-07-16 02:22:39 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,039,873
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a5840e7
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#4
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
0x1fe271b4
#8
forward
#9
setData
#10
withdraw
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x560ed681…07e6
0x34b655…2a6f
4 touches
1 conflict
0x836bdddc…0439
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x56f7a389…74fd
0x34b655…2a6f
4 touches
1 conflict
0x28d4261c…56c7
0x34b655…2a6f
4 touches
1 conflict
0xaeac6db9…7694
0x34b655…2a6f
4 touches
1 conflict
0xbf78ee7f…e7fd
0x34b655…2a6f
4 touches
1 conflict
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
0x560ed68159…1e07e6
Audit this contract →
← previous block
·
next block →
recent activity