pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,847,623
← previous block
next block →
recent activity
Analyzing
Block #93,847,623
11 transactions · 8 stateful · 2026-08-07 06:25:09 UTC
Parallelism
82
/100
Blocked
25
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,847,623
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x6a757abd
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 2
#5
execFwdPositionOps
· blocks 1
#7
forward
#9
0x6a757abd
#10
setData
#6
execFwdPositionOps
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x61b623aa…1540
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb1b58b33…874f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
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
0x261cbea79d…12e35d
Audit this contract →
← previous block
·
next block →
recent activity