pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,798,443
← previous block
next block →
recent activity
Analyzing
Block #101,798,443
11 transactions · 10 stateful · 2026-09-04 03:53:30 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,798,443
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
matchOrders
#3
updatePrices
#4
0x59558d29
#5
executeBatch
#6
setData
#7
execFwdPositionOpsV2
· blocks 1
#9
execOrders
#10
execOrders
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ee0b65a…6d40
0x34b655…2a6f
4 touches
1 conflict
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0x38a04dd1…8c24
0x34b655…2a6f
4 touches
1 conflict
0x5cb99fee…00cf
0x754704…b603
2 touches
0 conflicts
0x9673d1ed…005d
0x754704…b603
2 touches
0 conflicts
0x9ae4aa46…597f
0x754704…b603
2 touches
0 conflicts
0xde93ff88…37ec
0x754704…b603
2 touches
0 conflicts
0x00000000…004b
0x80c745…7210
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
0x4ee0b65a93…c56d40
Audit this contract →
← previous block
·
next block →
recent activity