pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,041,813
← previous block
next block →
recent activity
Analyzing
Block #71,041,813
9 transactions · 6 stateful · 2026-04-28 08:11:10 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,041,813
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1a945f9c
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
0x6463ffd1
· blocks 1
#6
0x69f06c16
#7
setData
#8
0x3ae1f1…1a59
#5
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x300b5e66…e568
0x065c9d…c394
4 touches
1 conflict
0x555403c1…df09
0x065c9d…c394
4 touches
1 conflict
0x95b86448…0d01
0x065c9d…c394
4 touches
1 conflict
0xe7032629…9525
0x065c9d…c394
4 touches
1 conflict
0xb6b74ae0…8d5e
0xea1b8e…c5ec
2 touches
0 conflicts
0xbc33a929…8b24
0xea1b8e…c5ec
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity