pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,137,030
← previous block
next block →
recent activity
Analyzing
Block #88,137,030
14 transactions · 13 stateful · 2026-07-16 13:12:33 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,137,030
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
0x6a58d938
#6
setData
#7
execOrders
#8
execOrders
· blocks 1
#9
execOrders
#10
execOrders
#11
execOrders
#12
execOrders
#13
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25ff7717…d4af
0x34b655…2a6f
4 touches
1 conflict
0x277cdc50…a5ec
0x34b655…2a6f
4 touches
1 conflict
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0x84849074…1ca2
0x34b655…2a6f
4 touches
1 conflict
0xaf1b5482…e72d
0x34b655…2a6f
4 touches
1 conflict
0xb88feea7…19fd
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xddd7607e…9b4b
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
0x25ff77178c…2ad4af
Audit this contract →
← previous block
·
next block →
recent activity