pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,453,080
← previous block
next block →
recent activity
Analyzing
Block #93,453,080
9 transactions · 8 stateful · 2026-08-05 21:21:42 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,453,080
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
matchOrders
#2
updateDataFeedsValuesPartial
#3
executeBatch
#4
placeAndExecuteMarketBuy
#5
execFwdPositionOps
· blocks 2
#8
setData
#6
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xabd0bcfc…64e2
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x3a27ed55…525b
0x34b655…2a6f
4 touches
1 conflict
0x6127c8ac…3f6e
0x34b655…2a6f
4 touches
1 conflict
0xde8a9295…0466
0x754704…b603
2 touches
0 conflicts
0x04a32684…1017
0x99c7a7…8bf0
2 touches
0 conflicts
0x7445e790…b2fc
0x99c7a7…8bf0
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
0xabd0bcfc80…a364e2
Audit this contract →
← previous block
·
next block →
recent activity