pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,223,053
← previous block
next block →
recent activity
Analyzing
Block #76,223,053
11 transactions · 7 stateful · 2026-05-22 08:15:48 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,223,053
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
0xab083028
· blocks 1
#4
updatePrices
#5
0x98717539
#6
updateDataFeedsValuesPartial
#7
setData
#8
0xcd177a…bf13
#9
0x8c7c79…4760
#10
0xa6c036…93e6
#3
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0xf1076cae…8efd
0x065c9d…c394
3 touches
1 conflict
0xfc819cf2…e38d
0x065c9d…c394
3 touches
1 conflict
0x51616fab…e066
0x065c9d…c394
2 touches
0 conflicts
0x5e583308…0369
0x065c9d…c394
2 touches
0 conflicts
0xadc6a61a…c66f
0x065c9d…c394
2 touches
0 conflicts
0xb673d3f6…cfb4
0x065c9d…c394
2 touches
0 conflicts
0xd9102b36…15e5
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
0xf3d7a307cc…f14d63
Audit this contract →
← previous block
·
next block →
recent activity