pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,307,449
← previous block
next block →
recent activity
Analyzing
Block #101,307,449
9 transactions · 9 stateful · 2026-09-02 10:43:21 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,307,449
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 2
#3
updateDataFeedsValuesPartial
#4
0x59558d29
#5
execOrder
#6
execFwdPositionOpsV2
#8
execOrders
#2
0xab083028
#7
0xc7068c7b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x7f9622bd…ef05
0xa6afd3…d132
4 touches
1 conflict
0x901b2a81…7af9
0xa6afd3…d132
4 touches
1 conflict
0x06d7243a…2d20
0x34ae4d…3fc5
2 touches
0 conflicts
0x10abefc9…c9bc
0x34ae4d…3fc5
2 touches
0 conflicts
0x1b9f9b78…a2b7
0x34ae4d…3fc5
2 touches
0 conflicts
0x2a981bf0…9528
0x34ae4d…3fc5
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