pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,291,058
← previous block
next block →
recent activity
Analyzing
Block #93,291,058
12 transactions · 11 stateful · 2026-08-05 07:47:07 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,291,058
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
setPrice
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
collect
#7
updateTemporalNumericValuesV1
#8
0x6a72eaf2
#9
setData
#10
execOrders
#11
0x59558d29
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x09790557…7c26
0x34b655…2a6f
2 touches
0 conflicts
0x107b89e4…470d
0x34b655…2a6f
2 touches
0 conflicts
0x37d710c8…45c1
0x34b655…2a6f
2 touches
0 conflicts
0x3e412550…5c60
0x34b655…2a6f
2 touches
0 conflicts
0x535cd929…07ce
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity