pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#71,343,117
← previous block
next block →
recent activity
Analyzing
Block #71,343,117
8 transactions · 8 stateful · 2026-04-29 17:37:31 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,343,117
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x1a945f9c
· blocks 1
#3
approve
#5
0x69f24253
#6
setData
#7
execOrders
#4
0xd10227eb
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x770a9350…bed9
0x065c9d…c394
2 touches
0 conflicts
0x89eca14d…b98c
0x065c9d…c394
2 touches
0 conflicts
0xa7923377…a0dc
0x065c9d…c394
2 touches
0 conflicts
0xa9eba2c1…a05e
0x065c9d…c394
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:
LeverUp: LeverUp
1 conflict on slot
0xa8abcc1955…203d83
Audit this contract →
← previous block
·
next block →
recent activity