pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,743,077
← previous block
next block →
recent activity
Analyzing
Block #71,743,077
11 transactions · 10 stateful · 2026-05-01 14:05:14 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,743,077
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x69f4b392
#3
updatePrices
· blocks 1
#5
0xeffdedb0
#6
0xeca0d6…dff9
#8
forward
#9
updateDataFeedsValuesPartial
#10
setData
#4
updatePrices
#7
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0xd09312c2…5ae1
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe59090da…6044
0x065c9d…c394
3 touches
1 conflict
0x2481307c…06e9
0x065c9d…c394
3 touches
1 conflict
0xb7b98fa7…e8f1
0x065c9d…c394
3 touches
1 conflict
0xd2592e76…4879
0x065c9d…c394
3 touches
1 conflict
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:
0x7e9d3a8a…4f9fda
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity