pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,488,712
← previous block
next block →
recent activity
Analyzing
Block #102,488,712
10 transactions · 10 stateful · 2026-09-06 14:08:29 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,488,712
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swap
#2
execOrders
#3
0xab083028
· blocks 1
#5
0xab083028
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
0x6a9d73e0
#4
0xab083028
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
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0ffac39e…6d34
0x34b655…2a6f
2 touches
0 conflicts
0x4f3cc09a…2804
0x34b655…2a6f
2 touches
0 conflicts
0x65f011a5…bc6e
0x34b655…2a6f
2 touches
0 conflicts
0x7a78012d…1603
0x34b655…2a6f
2 touches
0 conflicts
0x85a40730…6392
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0xaad6be10ae…2c0801
Audit this contract →
← previous block
·
next block →
recent activity