pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,787,656
← previous block
next block →
recent activity
Analyzing
Block #85,787,656
10 transactions · 7 stateful · 2026-07-05 15:29:01 UTC
Parallelism
70
/100
Blocked
29
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,787,656
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 2
#4
0x6df9e92b
#5
updateDataFeedsValuesPartial
#6
0x6a4a78b5
#7
setData
#8
0xf2cc23…1130
#9
0xccf720…f04d
#2
0xab083028
· blocks 1
#3
0x6ad2e98b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x36aa7ca2…1677
0x40c49f…2af0
2 touches
0 conflicts
0x63fb2d58…07b4
0x40c49f…2af0
2 touches
0 conflicts
0xd8edc3b2…9cef
0x40c49f…2af0
2 touches
0 conflicts
0xee660658…2445
0x40c49f…2af0
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
3 conflicts on slot
0x13a54fa2d3…a35ae3
Audit this contract →
← previous block
·
next block →
recent activity