pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,381,159
← previous block
next block →
recent activity
Analyzing
Block #70,381,159
9 transactions · 8 stateful · 2026-04-25 06:51:17 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,381,159
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
0xc27483…1b7c
#1
0xf246a8…82c4
#2
0x10c067…2877
· blocks 1
#3
0xa69e2b…b051
#4
0x4022d9…13f4
#6
0x6d43dc…2a62
#7
0x0f9d60…5678
#8
0x93bc02…0700
#5
0xd202c9…dc6d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
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
0x76756192…ec81
0x065c9d…c394
4 touches
1 conflict
0x8fc193f8…a756
0x065c9d…c394
4 touches
1 conflict
0xab17c902…bac6
0x065c9d…c394
4 touches
1 conflict
0xe58ac864…5593
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity