pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,483,071
← previous block
next block →
recent activity
Analyzing
Block #76,483,071
11 transactions · 10 stateful · 2026-05-23 13:07:12 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,483,071
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
· blocks 1
#3
0x5339c59f
#5
updateDataFeedsValuesPartial
#6
closeTrade
#7
updateTemporalNumericValuesV1
#8
0x6df9e92b
#9
transfer
#10
setData
#4
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb8d914cc…1f1f
0x065c9d…c394
4 touches
1 conflict
0x4520f577…c413
0x065c9d…c394
3 touches
1 conflict
0xaa55257a…6181
0x065c9d…c394
3 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0xf8480e2a…dff2
0x1b6862…e19c
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
0xb8d914cc08…011f1f
Audit this contract →
← previous block
·
next block →
recent activity