pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#71,042,661
← previous block
next block →
recent activity
Analyzing
Block #71,042,661
9 transactions · 8 stateful · 2026-04-28 08:16:49 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
#71,042,661
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
#2
0x6463ffd1
· blocks 1
#3
updatePriceFeedsIfNecessary
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
createGame
#8
setData
#4
0x6463ffd1
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
0x50e40524…51a0
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9339ddaf…6a11
0x065c9d…c394
4 touches
1 conflict
0x8609ff25…a4b7
0x065c9d…c394
4 touches
1 conflict
0x8c78769f…4c77
0x065c9d…c394
4 touches
1 conflict
0xb2a4885e…6f2d
0x065c9d…c394
3 touches
1 conflict
0x25de453d…9573
0x34b655…2a6f
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
0x50e4052431…8651a0
Audit this contract →
← previous block
·
next block →
recent activity