pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,243,319
← previous block
next block →
recent activity
Analyzing
Block #71,243,319
11 transactions · 11 stateful · 2026-04-29 06:32:44 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,243,319
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swap
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
0x6463ffd1
· blocks 1
#5
0x0c7abd22
#6
0x0c7abd22
#8
forward
#9
0x69f1a684
#10
setData
#7
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd53e2c7…fe6e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7a5bb1dd…69f0
0x065c9d…c394
4 touches
1 conflict
0x999d60fe…4992
0x065c9d…c394
4 touches
1 conflict
0xb5e1e18f…5936
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x46cb45de…a568
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0000
0x2d82ac…5fd8
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
0xcd53e2c7f4…d7fe6e
Audit this contract →
← previous block
·
next block →
recent activity