pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,556,812
← previous block
next block →
recent activity
Analyzing
Block #93,556,812
11 transactions · 9 stateful · 2026-08-06 06:03:10 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,556,812
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
updatePrices
#4
0x5acec890
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
setData
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe196f841…22e3
0x34b655…2a6f
4 touches
1 conflict
0xe196f841…22e4
0x34b655…2a6f
4 touches
1 conflict
0x3fead0ae…0e35
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xd077a617…2f11
0x34b655…2a6f
4 touches
1 conflict
0x3ea25e92…a36d
0x34b655…2a6f
2 touches
0 conflicts
0x4b13022d…dc04
0x34b655…2a6f
2 touches
0 conflicts
0x734f015b…a702
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
0xe196f8419b…9322e3
Audit this contract →
← previous block
·
next block →
recent activity