pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,249,831
← previous block
next block →
recent activity
Analyzing
Block #80,249,831
12 transactions · 10 stateful · 2026-06-09 23:54:24 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,249,831
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5339c59f
#2
0x5339c59f
· blocks 1
#3
0xab083028
#4
0xed82b078
· blocks 1
#6
updateDataFeedsValuesPartial
#7
executeBatch
#8
0x29eed2d3
#9
0x6a28a828
#10
setData
#11
0x37ebb2…83fb
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x07443cfb…0e2d
0x065c9d…c394
2 touches
0 conflicts
0x80afd9d9…57cf
0x065c9d…c394
2 touches
0 conflicts
0xbd7662a3…f550
0x065c9d…c394
2 touches
0 conflicts
0xcc4b3371…b355
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
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
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity