pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,577,387
← previous block
next block →
recent activity
Analyzing
Block #83,577,387
11 transactions · 11 stateful · 2026-06-25 09:55:01 UTC
Parallelism
73
/100
Blocked
27
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,577,387
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
addSellOrder
· blocks 2
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
forward
#7
0x6a3cfb6c
#8
setData
#9
execOrders
· blocks 1
#2
batchCancelOrders
· blocks 1
#10
execOrders
#3
batchCancelOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cd6928f…1a19
0x2a68ba…90c5
6 touches
3 conflicts
0x2efc4b1d…474b
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x3712f087…8b85
0xa6afd3…d132
4 touches
1 conflict
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0xc8fec9ca…2d60
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xa51de3df…c65a
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot
0x4cd6928f0d…fd1a19
Audit this contract →
← previous block
·
next block →
recent activity