pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,324,559
← previous block
next block →
recent activity
Analyzing
Block #86,324,559
13 transactions · 11 stateful · 2026-07-08 03:11:28 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,324,559
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0d484c28
#2
0xab083028
· blocks 1
#4
0xab083028
#5
updatePrices
#6
0x39435dac
#7
0x39435dac
#8
0x0f6795d9
#9
0x5339c59f
#10
updateDataFeedsValuesPartial
#11
setData
#12
0x39435dac
#3
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x022ae86a…3125
0x01bff4…1071
2 touches
0 conflicts
0x11b69a7e…334e
0x01bff4…1071
2 touches
0 conflicts
0x56a919c4…ab49
0x01bff4…1071
2 touches
0 conflicts
0x5948f6e6…42c4
0x01bff4…1071
2 touches
0 conflicts
0xed67cadc…c62e
0x01bff4…1071
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
0x13a54fa2d3…a35ae3
Audit this contract →
← previous block
·
next block →
recent activity