pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,242,583
← previous block
next block →
recent activity
Analyzing
Block #93,242,583
11 transactions · 10 stateful · 2026-08-05 03:43:22 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,242,583
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
0xb2d4797b
#6
0x3f5c179b
#7
0x6a72b1d2
#8
setData
#10
0xc7e3ec2c
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd79e9cac…9f72
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x03a6363b…ad2b
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x286711a5…b3bf
0x34b655…2a6f
2 touches
0 conflicts
0x3ba2a9aa…d3d4
0x34b655…2a6f
2 touches
0 conflicts
0x3e125b49…dcc7
0x34b655…2a6f
2 touches
0 conflicts
0x565326bb…ae7e
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
0xd79e9cacba…529f72
Audit this contract →
← previous block
·
next block →
recent activity