pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,340,071
← previous block
next block →
recent activity
Analyzing
Block #88,340,071
10 transactions · 9 stateful · 2026-07-17 11:51:04 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,340,071
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xdb834625
#2
execFwdPositionOps
· blocks 2
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#6
forward
#7
0x6a5a17a0
#8
setData
#5
execFwdPositionOps
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x745952b2…d90c
0x34b655…2a6f
6 touches
3 conflicts
0x7cd78950…607c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xc6c566e1…a6fa
0x34b655…2a6f
4 touches
1 conflict
0x28db33af…4bc4
0x34b655…2a6f
2 touches
0 conflicts
0x373739ed…a7ee
0x34b655…2a6f
2 touches
0 conflicts
0x38948e75…437a
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
0x745952b2a0…a6d90c
Audit this contract →
← previous block
·
next block →
recent activity