pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,304,984
← previous block
next block →
recent activity
Analyzing
Block #94,304,984
12 transactions · 11 stateful · 2026-08-08 20:53:02 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,304,984
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallOnEpochChange
#1
syscallReward
#2
0x0c7abd22
#3
0x5acec890
#4
execFwdPositionOps
#5
execFwdPositionOps
· blocks 1
#6
0x3f5c179b
#7
placeAndExecuteMarketSell
· blocks 1
#10
updateDataFeedsValuesPartial
#11
setData
#8
batchUpdate
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w0
8
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a9e9bd1…5368
0x2a68ba…90c5
4 touches
1 conflict
0x1279ed80…4a27
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x9dd86c1e…f0a8
0xa6afd3…d132
3 touches
1 conflict
0x0a000000…0000
0x000000…1000
2 touches
0 conflicts
0x0a000000…0000
0x000000…1000
2 touches
0 conflicts
0x0a000000…0000
0x000000…1000
2 touches
0 conflicts
0x0a000000…0000
0x000000…1000
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
0x2a9e9bd1e2…355368
Audit this contract →
← previous block
·
next block →
recent activity