pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#71,043,216
← previous block
next block →
recent activity
Analyzing
Block #71,043,216
11 transactions · 10 stateful · 2026-04-28 08:20:32 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
#71,043,216
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
0x4500f50f
· blocks 2
#3
0xd60faa87
#5
updatePrices
#6
updateDataFeedsValuesPartial
#7
setData
#9
0x0c7abd22
#10
0x69f06e47
#4
0x76368669
#8
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0x0714df05…bab9
0x065c9d…c394
3 touches
1 conflict
0x446f2734…8b54
0x0a3323…0a3c
2 touches
0 conflicts
0xff393f19…4dd2
0x0a3323…0a3c
2 touches
0 conflicts
0x00000000…0000
0x0d73bf…be07
2 touches
0 conflicts
0x00000000…0001
0x0d73bf…be07
2 touches
0 conflicts
0x00000000…0003
0x0d73bf…be07
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:
USDC (USDC)
1 conflict on slot
0x17606ba612…ea1b6e
Audit this contract →
← previous block
·
next block →
recent activity