pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#71,648,551
← previous block
next block →
recent activity
Analyzing
Block #71,648,551
11 transactions · 8 stateful · 2026-05-01 03:35:47 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,648,551
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x5bf9264c
· blocks 1
#4
0xeffdedb0
#5
0x9036287a
#6
setData
#7
0x98717539
#8
0x69f4200b
#9
0x6b0456…9069
#10
0x5348d5…6827
#3
0x5bf9264c
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
0xc824469a…641c
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x1a4b4152…0a08
0x33663b…4897
2 touches
0 conflicts
0x2e2214a9…fe0d
0x33663b…4897
2 touches
0 conflicts
0x3e4b8d9f…b8a7
0x33663b…4897
2 touches
0 conflicts
0x50997ada…364d
0x33663b…4897
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:
Perpl
1 conflict on slot
0xc824469a90…af641c
Audit this contract →
← previous block
·
next block →
recent activity