pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,584,125
← previous block
next block →
recent activity
Analyzing
Block #83,584,125
12 transactions · 12 stateful · 2026-06-25 10:39:52 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,584,125
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
batchUpdate
#2
batchUpdate
· blocks 1
#3
batchUpdate
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x0f6795d9
#8
0x0f6795d9
#9
0x6a3d05ef
#10
setData
#11
0xc7e3ec2c
#4
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x3817764d…242b
0x34b655…2a6f
2 touches
0 conflicts
0x39451527…ad86
0x34b655…2a6f
2 touches
0 conflicts
0x53122a4f…f4d1
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
0x5581d709b4…95ab77
Audit this contract →
← previous block
·
next block →
recent activity