pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,421,706
← previous block
next block →
recent activity
Analyzing
Block #71,421,706
8 transactions · 5 stateful · 2026-04-30 02:21:26 UTC
Parallelism
63
/100
Blocked
40
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,421,706
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x05ee6a22
#4
updateDataFeedsValuesPartial
#6
setData
#7
jMMeC
#2
0x0c7abd22
· blocks 1
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x4e04179e…7ab8
0xd32edf…ff58
3 touches
1 conflict
0x4cb45bca…e0fd
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21c6
0x1b6862…e19c
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
0x92d610a6f9…379a40
Audit this contract →
← previous block
·
next block →
recent activity