pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,864,399
← previous block
next block →
recent activity
Analyzing
Block #90,864,399
9 transactions · 8 stateful · 2026-07-27 20:14:53 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,864,399
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#4
0x6a67bcb4
#5
setData
#6
execOrders
· blocks 1
#7
execOrders
#3
execFwdPositionOps
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc93761d9…cfdf
0x34b655…2a6f
4 touches
1 conflict
0xd5c98027…9fd9
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x044844a0…7418
0x34b655…2a6f
4 touches
1 conflict
0x0d488000…3831
0x34b655…2a6f
4 touches
1 conflict
0x0db691ab…3ee3
0x34b655…2a6f
4 touches
1 conflict
0x18e86f02…fa98
0x34b655…2a6f
4 touches
1 conflict
0x2a38297c…67c8
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
0xc93761d95d…d2cfdf
Audit this contract →
← previous block
·
next block →
recent activity