pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,556,043
← previous block
next block →
recent activity
Analyzing
Block #71,556,043
11 transactions · 9 stateful · 2026-04-30 17:20:10 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,556,043
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f38fc1
#2
updatePrices
· blocks 1
#4
0xe7be4706
#5
0xeffdedb0
#6
0xe7be4706
#7
0xe7be4706
· blocks 1
#9
updateDataFeedsValuesPartial
#10
setData
#3
updatePrices
#8
0xe7be4706
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6455d1f…1029
0x754704…b603
4 touches
1 conflict
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0x0d0b2509…074d
0x3bd359…433a
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x78ae17f2…53be
0x000000…012a
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x00000000…0001
0x010592…1c83
2 touches
0 conflicts
0xc5c4c1d1…2145
0x3bd359…433a
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:
0x754704bc…afb603
1 conflict on slot
0xe6455d1fbe…eb1029
Audit this contract →
← previous block
·
next block →
recent activity