pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,855,677
← previous block
next block →
recent activity
Analyzing
Block #93,855,677
10 transactions · 8 stateful · 2026-08-07 07:05:38 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,855,677
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
#3
execPerpOps
#4
execPerpOps
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
· blocks 1
#8
0x6a75843a
#9
setData
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x04e53004…1b3b
0x34b655…2a6f
2 touches
0 conflicts
0x09149faa…1b1d
0x34b655…2a6f
2 touches
0 conflicts
0x261cbea7…e35d
0x34b655…2a6f
2 touches
0 conflicts
0x261cbea7…e35e
0x34b655…2a6f
2 touches
0 conflicts
0x39fb42f2…35f2
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
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity