pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,335,599
← previous block
next block →
recent activity
Analyzing
Block #74,335,599
12 transactions · 10 stateful · 2026-05-13 14:10:05 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,335,599
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
setData
#5
0x6df9e92b
· blocks 1
#7
forward
#8
0x5339c59f
#9
0x5339c59f
#10
0xed82b078
#11
jMMeC
#6
0xec2bd3f2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x019883…2a9a
2 touches
0 conflicts
0x00000000…0002
0x019883…2a9a
2 touches
0 conflicts
0x00000000…0003
0x019883…2a9a
2 touches
0 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
2 touches
0 conflicts
0xf0c05263…9a0d
0x0cc9b2…7777
2 touches
0 conflicts
0x00000000…0000
0x139aab…382b
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:
0x3bd359c1…15433a
1 conflict on slot
0xa472d565a0…ae9fe4
Audit this contract →
← previous block
·
next block →
recent activity