pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,685,385
← previous block
next block →
recent activity
Analyzing
Block #90,685,385
8 transactions · 7 stateful · 2026-07-27 05:14:11 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,685,385
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
#3
execFwdPositionOps
#4
setData
#5
execOrders
· blocks 1
#7
0xc7e3ec2c
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x03bf1a82…9118
0x34b655…2a6f
2 touches
0 conflicts
0x03bf1a82…9119
0x34b655…2a6f
2 touches
0 conflicts
0x0985d601…c9fa
0x34b655…2a6f
2 touches
0 conflicts
0x0f1db0b4…a3ee
0x34b655…2a6f
2 touches
0 conflicts
0x1a625e4c…7274
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity