pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,856,903
← previous block
next block →
recent activity
Analyzing
Block #90,856,903
11 transactions · 11 stateful · 2026-07-27 19:37:07 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,856,903
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
· blocks 1
#3
0x5a5d9a99
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
executeBatch
#7
0x3f5c179b
#8
setData
#10
0xc7e3ec2c
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde9d38a8…4c0f
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3ea25e92…a36d
0x34b655…2a6f
2 touches
0 conflicts
0x46bd640f…5424
0x34b655…2a6f
2 touches
0 conflicts
0x48115a33…a2d2
0x34b655…2a6f
2 touches
0 conflicts
0x526dcf24…1100
0x34b655…2a6f
2 touches
0 conflicts
0x5e47cbde…9659
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
0xde9d38a88f…994c0f
Audit this contract →
← previous block
·
next block →
recent activity