pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,090,027
← previous block
next block →
recent activity
Analyzing
Block #71,090,027
12 transactions · 11 stateful · 2026-04-28 13:32:22 UTC
Parallelism
75
/100
Blocked
27
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,090,027
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
increaseLiquidity
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
0x6463ffd1
· blocks 3
#5
0x6df9e92b
#9
setData
#10
updatePrices
#11
updatePrices
#6
0xed82b078
· blocks 1
#7
0xed82b078
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d7a307…4d63
0x065c9d…c394
6 touches
3 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x1be73d2c…acd9
0x3bd359…433a
2 touches
0 conflicts
0x51ca3051…0972
0x3bd359…433a
2 touches
0 conflicts
0xa299e0e2…bbdd
0x46a15b…4364
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
3 conflicts on slot
0xf3d7a307cc…f14d63
Audit this contract →
← previous block
·
next block →
recent activity