pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,296,644
← previous block
next block →
recent activity
Analyzing
Block #80,296,644
8 transactions · 8 stateful · 2026-06-10 05:06:23 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,296,644
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5339c59f
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x98717539
#6
0x3f5c179b
#7
setData
#2
0xed82b078
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
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0xe41f8863…29a4
0xa6afd3…d132
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x25d30ad6…a8ec
0x34b655…2a6f
2 touches
0 conflicts
0x35a92bbe…e17d
0x34b655…2a6f
2 touches
0 conflicts
0x63b74d88…b6ca
0x34b655…2a6f
2 touches
0 conflicts
0x6f988a4a…b39f
0x34b655…2a6f
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
0xb3572c958a…0d9c4a
Audit this contract →
← previous block
·
next block →
recent activity