pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,996,582
← previous block
next block →
recent activity
Analyzing
Block #70,996,582
10 transactions · 10 stateful · 2026-04-28 03:10:10 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,996,582
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
· blocks 1
#4
0x98717539
#5
0x6463ffd1
· blocks 1
#7
forward
#8
0x69f02589
#9
setData
#3
updatePrices
#6
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x188a7cc8…f2e9
0x065c9d…c394
4 touches
1 conflict
0x1a5d70a4…3428
0x065c9d…c394
4 touches
1 conflict
0x5ce324b7…0a1e
0x065c9d…c394
4 touches
1 conflict
0xa04b815a…14db
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 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:
0xb857c13a…1a9be1
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity