pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,362,035
← previous block
next block →
recent activity
Analyzing
Block #93,362,035
12 transactions · 12 stateful · 2026-08-05 13:43:58 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,362,035
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#3
depositV3
#4
execFwdPositionOps
#5
0xc0c16b76
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
commit
#10
setData
#11
0x59558d29
#2
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b3cfc56…2a4a
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2385516f…eca5
0x34b655…2a6f
2 touches
0 conflicts
0x28466a40…ad26
0x34b655…2a6f
2 touches
0 conflicts
0x28c180e1…f1e2
0x34b655…2a6f
2 touches
0 conflicts
0x297e9342…3292
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
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
0x0b3cfc56e9…112a4a
Audit this contract →
← previous block
·
next block →
recent activity