pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,341,752
← previous block
next block →
recent activity
Analyzing
Block #74,341,752
11 transactions · 10 stateful · 2026-05-13 14:51:02 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,341,752
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1094dc9f
· blocks 2
#2
updateDataFeedsValuesPartial
#3
removeLiquidity
#4
updatePrices
#5
setData
#6
0x6df9e92b
#7
forward
#10
cancel
#8
0x5339c59f
#9
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xa14d8a1d…c612
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x404314de…df1a
0x3bd359…433a
2 touches
0 conflicts
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0xc5c4c1d1…2145
0x3bd359…433a
2 touches
0 conflicts
0xfe3bddd2…8b48
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
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
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity