pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#71,701,004
← previous block
next block →
recent activity
Analyzing
Block #71,701,004
10 transactions · 8 stateful · 2026-05-01 09:25:00 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,701,004
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0x1094dc9f
· blocks 1
#3
updatePrices
#4
0x0c7abd22
#5
0xeffdedb0
#7
setData
#8
0x39435dac
#9
0x39435dac
#6
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0xcd4a8c31…0772
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x76498d82…2995
0x000000…012a
2 touches
0 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
2 touches
0 conflicts
0x00f7e3b7…e017
0x188d58…ea8e
2 touches
0 conflicts
0x00f7e3b7…e018
0x188d58…ea8e
2 touches
0 conflicts
0x19fd1250…1b7a
0x188d58…ea8e
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:
0x2a68ba18…8e90c5
1 conflict on slot
0xc3c8642ae9…317da5
Audit this contract →
← previous block
·
next block →
recent activity