pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,311,556
← previous block
next block →
recent activity
Analyzing
Block #80,311,556
12 transactions · 10 stateful · 2026-06-10 06:45:56 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,311,556
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
deposit
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x98717539
#5
0x3f5c179b
#6
0x3f5c179b
#7
forward
#8
0x6a29089b
#9
0x6a29089b
#10
cancelTournament
#11
setData
#2
0x40e79b1b
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
0x6d383d1f…a65e
0x2a68ba…90c5
2 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
0x22aa3c9e…ee21
0x065c9d…c394
2 touches
0 conflicts
0xab87537e…78bb
0x065c9d…c394
2 touches
0 conflicts
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x25d30ad6…a8ec
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
0x6d383d1fcb…18a65e
Audit this contract →
← previous block
·
next block →
recent activity