pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,066,027
← previous block
next block →
recent activity
Analyzing
Block #102,066,027
8 transactions · 7 stateful · 2026-09-05 02:26:22 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,066,027
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
0xab083028
· blocks 1
#4
execFwdPositionOpsV2
#5
execFwdPositionOpsV2
#6
0x6a9b7dd2
#3
0xab083028
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
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
0xd02ebff8…fe31
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01315072…0e2d
0x34b655…2a6f
2 touches
0 conflicts
0x04958840…4276
0x34b655…2a6f
2 touches
0 conflicts
0x0bedffef…4531
0x34b655…2a6f
2 touches
0 conflicts
0x10a94122…c9c6
0x34b655…2a6f
2 touches
0 conflicts
0x14d3bb13…5cff
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