pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,453,419
← previous block
next block →
recent activity
Analyzing
Block #93,453,419
9 transactions · 9 stateful · 2026-08-05 21:23:25 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,453,419
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#5
placeAndExecuteMarketBuy
#6
0x6a73aa44
#7
setData
#8
0x59558d29
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe21234e7…bded
0x34b655…2a6f
4 touches
1 conflict
0x27680977…85ae
0x34b655…2a6f
4 touches
1 conflict
0x428b6e5b…8909
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0b710c61…e052
0x34b655…2a6f
2 touches
0 conflicts
0x0d7d817f…6eee
0x34b655…2a6f
2 touches
0 conflicts
0x0ddf4a4b…eb79
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
0xe21234e760…98bded
Audit this contract →
← previous block
·
next block →
recent activity