pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,243,745
← previous block
next block →
recent activity
Analyzing
Block #71,243,745
7 transactions · 6 stateful · 2026-04-29 06:35:34 UTC
Parallelism
43
/100
Blocked
50
%
Avg conflicts / tx
0.86
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,243,745
· 7 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x6463ffd1
· blocks 3
#6
setData
#3
0x6463ffd1
· blocks 2
#4
0x6463ffd1
· blocks 1
#5
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0xd0f8a6…badc
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xace514f7…0e98
0x065c9d…c394
6 touches
4 conflicts
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0x467c0bcf…92da
0x065c9d…c394
3 touches
1 conflict
0xc7eb78e4…3e61
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
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:
0xd0f8a642…83badc
6 conflicts on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity