pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,395,799
← previous block
next block →
recent activity
Analyzing
Block #74,395,799
9 transactions · 8 stateful · 2026-05-13 20:50:41 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,395,799
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x1ffa3c9b
· blocks 2
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
setData
#6
0x98717539
#8
withdraw
#2
0xed82b078
· blocks 1
#7
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47b807a2…3307
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x7f045645…cf5f
0x065c9d…c394
4 touches
1 conflict
0x264bb096…3e93
0x065c9d…c394
2 touches
0 conflicts
0x2679d88a…c163
0x065c9d…c394
2 touches
0 conflicts
0x5794046b…625c
0x065c9d…c394
2 touches
0 conflicts
0x69a50c6a…7e9c
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
3 conflicts on slot
0x47b807a243…c53307
Audit this contract →
← previous block
·
next block →
recent activity