pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,465,318
← previous block
next block →
recent activity
Analyzing
Block #76,465,318
11 transactions · 10 stateful · 2026-05-23 11:08:55 UTC
Parallelism
82
/100
Blocked
30
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,465,318
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xcf7468f4
#2
0xed82b078
· blocks 2
#3
0xab083028
· blocks 1
#7
updateDataFeedsValuesPartial
#8
updatePosition
#9
0x366fe5db
#10
setData
#4
0x5339c59f
#5
0x5339c59f
#6
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x99a4d286…ad43
0xa6afd3…d132
4 touches
1 conflict
0xc3afb222…4d17
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0c944eef…c96a
0x065c9d…c394
2 touches
0 conflicts
0x16d2822c…61ec
0x065c9d…c394
2 touches
0 conflicts
0x18cf3003…51d1
0x065c9d…c394
2 touches
0 conflicts
0x465a30d6…e2ca
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: Market-MON/USDC
1 conflict on slot
0xcc8faac238…88c766
Audit this contract →
← previous block
·
next block →
recent activity