pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,577,039
← previous block
next block →
recent activity
Analyzing
Block #83,577,039
10 transactions · 10 stateful · 2026-06-25 09:52:42 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,577,039
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
batchUpdate
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x6a3cfae2
#5
addSellOrder
· blocks 1
#7
setData
#8
executeBatch
#9
0xc7e3ec2c
#2
0xed82b078
#6
addSellOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cd6928f…1a19
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x668c9c7c…2aed
0xa6afd3…d132
3 touches
1 conflict
0x67726f49…6ede
0xa6afd3…d132
3 touches
1 conflict
0x3fff1fe4…7087
0x065c9d…c394
2 touches
0 conflicts
0xadbcf64f…a1b9
0x065c9d…c394
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
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
0x4cd6928f0d…fd1a19
Audit this contract →
← previous block
·
next block →
recent activity