pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,328,727
← previous block
next block →
recent activity
Analyzing
Block #93,328,727
11 transactions · 10 stateful · 2026-08-05 10:56:30 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,328,727
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
artefact_keep
#5
execFwdPositionOps
#6
execFwdPositionOps
· blocks 1
#8
0x3f5c179b
#9
setData
#10
0x59558d29
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b3c1134…cbf4
0x34b655…2a6f
4 touches
1 conflict
0xa69ba9e8…e56a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0610892c…fee0
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x674b4455…1d50
0x34b655…2a6f
2 touches
0 conflicts
0x7da56943…9753
0x34b655…2a6f
2 touches
0 conflicts
0x827557c1…a6be
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
0x6b3c1134cc…54cbf4
Audit this contract →
← previous block
·
next block →
recent activity