pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,158,075
← previous block
next block →
recent activity
Analyzing
Block #88,158,075
11 transactions · 11 stateful · 2026-07-16 15:33:30 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,158,075
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
0x6a58fa41
#5
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
setData
#6
execFwdPositionOps
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w0
6
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa2a27f2…d53b
0x34b655…2a6f
4 touches
1 conflict
0x634daab4…dd5e
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf28082df…312c
0x34b655…2a6f
4 touches
1 conflict
0x67185120…f565
0x34b655…2a6f
2 touches
0 conflicts
0x7585925a…3f45
0x34b655…2a6f
2 touches
0 conflicts
0x7c0bdc54…9dde
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
0xaa2a27f234…14d53b
Audit this contract →
← previous block
·
next block →
recent activity