pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,701,337
← previous block
next block →
recent activity
Analyzing
Block #71,701,337
8 transactions · 7 stateful · 2026-05-01 09:27:13 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,701,337
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
· blocks 1
#3
0xeffdedb0
#4
updateDataFeedsValuesPartial
#5
0x0c7abd22
#7
setData
#2
0xcf7468f4
· blocks 1
#6
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x846f2172…fd54
0x0555e3…2b9c
4 touches
1 conflict
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0xa3d02ee9…85c5
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x7f975651…8c28
0x0555e3…2b9c
2 touches
0 conflicts
0x46cb45de…a566
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:
0x0555e30d…0d2b9c
1 conflict on slot
0x846f21722e…fdfd54
Audit this contract →
← previous block
·
next block →
recent activity