pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,996,710
← previous block
next block →
recent activity
Analyzing
Block #70,996,710
11 transactions · 11 stateful · 2026-04-28 03:11:01 UTC
Parallelism
73
/100
Blocked
27
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,996,710
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x67098489
#2
0x98717539
· blocks 2
#4
0x98717539
#6
0x0c7abd22
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
· blocks 1
#3
0x98717539
· blocks 1
#10
0x39435dac
#5
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w2
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x8d66a4…3095
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1ac
0x8d66a4…3095
5 touches
3 conflicts
0x3702b140…97ea
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1a8
0x8d66a4…3095
4 touches
1 conflict
0x00f245ce…1e10
0x34b655…2a6f
4 touches
1 conflict
0xe89e1a22…ce49
0x8d66a4…3095
3 touches
1 conflict
0x03924cd3…f268
0x8d66a4…3095
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:
0x8d66a43f…113095
3 conflicts on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity