pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,289,121
← previous block
next block →
recent activity
Analyzing
Block #71,289,121
8 transactions · 7 stateful · 2026-04-29 11:37:34 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,289,121
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x20601463
· blocks 1
#2
0x98717539
· blocks 1
#4
updateDataFeedsValuesPartial
#6
setData
#7
0x39435dac
#3
0x98717539
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f430e47…4cbd
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1aa
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1ad
0x8d66a4…3095
4 touches
1 conflict
0xe89e1a22…ce49
0x8d66a4…3095
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xde38584a…ecb7
0x2a68ba…90c5
2 touches
0 conflicts
0x0175b7a6…1db9
0x7dfaf7…bf6a
2 touches
0 conflicts
0x0175b7a6…1dbc
0x7dfaf7…bf6a
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:
0x8d66a43f…113095
1 conflict on slot
0x7f430e471f…4e4cbd
Audit this contract →
← previous block
·
next block →
recent activity