pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#81,201,447
← previous block
next block →
recent activity
Analyzing
Block #81,201,447
10 transactions · 7 stateful · 2026-06-14 09:38:07 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,201,447
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#3
executeBatch
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x6a2e76f6
#7
setData
#8
0x5d9a3c…6b0b
#9
0x9525ec…f220
#2
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
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
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x053d5b4c…25de
0x40c49f…2af0
2 touches
0 conflicts
0x29bd9ce4…2c46
0x40c49f…2af0
2 touches
0 conflicts
0x467f7fed…964d
0x40c49f…2af0
2 touches
0 conflicts
0x84185e52…0e83
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
1 conflict on slot
0x13a54fa2d3…a35ae3
Audit this contract →
← previous block
·
next block →
recent activity