pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,189,327
← previous block
next block →
recent activity
Analyzing
Block #106,189,327
16 transactions · 10 stateful · 2026-09-19 13:29:52 UTC
Parallelism
88
/100
Blocked
10
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,189,327
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x67098489
#2
0xab083028
· blocks 1
#3
0xab083028
#4
0x5acec890
#5
0x5acec890
#7
execOrders
#8
0x59558d29
#9
0x59558d29
#10
sweepNative
#11
0x1ea3e879
#12
setData
#13
execFwdPositionOpsV2
#14
execOrders
#15
execOrders
#6
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
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
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x18cf3003…51d1
0x065c9d…c394
2 touches
0 conflicts
0xcc8faac2…c766
0x065c9d…c394
2 touches
0 conflicts
0xd58a5e97…a0d8
0x065c9d…c394
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
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