pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,502,078
← previous block
next block →
recent activity
Analyzing
Block #101,502,078
12 transactions · 10 stateful · 2026-09-03 03:02:42 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,502,078
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
execOrders
· blocks 1
#4
execPerpOps
#5
execPerpOps
#6
0x0c7abd22
#7
updateDataFeedsValuesPartial
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
setData
#11
execOrders
#3
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0f85a40a…7e31
0x34b655…2a6f
2 touches
0 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
2 touches
0 conflicts
0x25f658fb…6eba
0x34b655…2a6f
2 touches
0 conflicts
0x3040889b…532b
0x34b655…2a6f
2 touches
0 conflicts
0x310a7246…2dcb
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
0xbde524f475…b143bf
Audit this contract →
← previous block
·
next block →
recent activity