pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,855,901
← previous block
next block →
recent activity
Analyzing
Block #93,855,901
11 transactions · 11 stateful · 2026-08-07 07:06:46 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,855,901
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
0x6a75847d
#9
transfer
#10
setData
#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
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x33f54bd6…9ac3
0x34b655…2a6f
4 touches
1 conflict
0x8299fe6c…5752
0x34b655…2a6f
4 touches
1 conflict
0x3a7091da…f2eb
0x34b655…2a6f
2 touches
0 conflicts
0x46870010…0b51
0x34b655…2a6f
2 touches
0 conflicts
0x64e78a02…e340
0x34b655…2a6f
2 touches
0 conflicts
0xbde524f4…43bf
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