pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#81,018,276
← previous block
next block →
recent activity
Analyzing
Block #81,018,276
7 transactions · 6 stateful · 2026-06-13 13:17:51 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#81,018,276
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0xa09e9040
· blocks 1
#4
setData
#5
0x6a2d58f7
#6
0x785f5745
#3
0x23afbff3
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
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1c30fc6e…59de
0x065c9d…c394
2 touches
0 conflicts
0x4a313a9c…6f13
0x065c9d…c394
2 touches
0 conflicts
0xa0f7c4cf…2f33
0x065c9d…c394
2 touches
0 conflicts
0xebf53b76…af8c
0x065c9d…c394
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
0xd8dd03ce37…9cdc8d
Audit this contract →
← previous block
·
next block →
recent activity