pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,201,422
← previous block
next block →
recent activity
Analyzing
Block #95,201,422
13 transactions · 11 stateful · 2026-08-12 00:12:57 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,201,422
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x41a8f47c
· blocks 1
#2
0xab083028
#3
0x5acec890
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
executeBatch
#8
execFwdPositionOps
#9
execOrders
#10
transfer
#11
setData
#12
0x59558d29
#7
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x96e53d21…29d4
0x40c49f…2af0
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x5d601639…d720
0x5dd8f3…c69c
2 touches
0 conflicts
0x0b552eae…fbd9
0x754704…b603
2 touches
0 conflicts
0x4e858410…6ba5
0x754704…b603
2 touches
0 conflicts
0x69c8bf4a…2ed0
0x754704…b603
2 touches
0 conflicts
0x996286b4…54d2
0x754704…b603
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
0x002fed350f…7379fa
Audit this contract →
← previous block
·
next block →
recent activity