pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,040,193
← previous block
next block →
recent activity
Analyzing
Block #88,040,193
8 transactions · 8 stateful · 2026-07-16 02:24:48 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,040,193
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#5
0x6a584167
#6
setData
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f1ad4b4…e00a
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x013bdb87…85b3
0x34b655…2a6f
2 touches
0 conflicts
0x0dd4c889…b62d
0x34b655…2a6f
2 touches
0 conflicts
0x1232aa2b…bc8a
0x34b655…2a6f
2 touches
0 conflicts
0x20d33f08…5249
0x34b655…2a6f
2 touches
0 conflicts
0x310afe2c…83e1
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
0x4f1ad4b4ec…b9e00a
Audit this contract →
← previous block
·
next block →
recent activity