pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,892,377
← previous block
next block →
recent activity
Analyzing
Block #70,892,377
10 transactions · 9 stateful · 2026-04-27 15:36:08 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,892,377
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0x0d484c28
· blocks 1
#3
revealWithCallback
#4
updateDataFeedsValuesPartial
#7
0x69ef82df
#8
setData
#9
0x36326531
#5
0x6463ffd1
· blocks 1
#6
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0633faef…6470
0x065c9d…c394
4 touches
1 conflict
0x6aca9b90…5112
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5f7064fd…fa0f
0x065c9d…c394
4 touches
1 conflict
0x1bfe4191…e29b
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x5bc759fc…c5b1
0x065c9d…c394
3 touches
1 conflict
0x00000000…002c
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:
0x065c9d28…a9c394
1 conflict on slot
0x0633faef92…f96470
Audit this contract →
← previous block
·
next block →
recent activity