pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,332,125
← previous block
next block →
recent activity
Analyzing
Block #84,332,125
12 transactions · 10 stateful · 2026-06-28 21:46:27 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,332,125
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x5a5d9a99
#3
execFwdPositionOps
#4
metacall
#5
executeBatch
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
0xed82b078
· blocks 1
#10
0x6a4196ab
#11
setData
#9
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xc05b880b…7746
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0001
0x2da28f…75e8
2 touches
0 conflicts
0x00000000…0003
0x2da28f…75e8
2 touches
0 conflicts
0xf334fe53…11d8
0x2da28f…75e8
2 touches
0 conflicts
0x06413b92…f0c3
0x34b655…2a6f
2 touches
0 conflicts
0x0833f1ab…71e7
0x34b655…2a6f
2 touches
0 conflicts
0x7c6984da…21e5
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
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity