pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,627,472
← previous block
next block →
recent activity
Analyzing
Block #74,627,472
12 transactions · 8 stateful · 2026-05-14 22:40:33 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,627,472
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
0x98717539
#6
forward
#7
0x6df9e92b
· blocks 1
#9
setData
#10
0x813d20…95a2
#11
0x990e65…6cc8
#8
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x86dfd5…6a7d
4 touches
1 conflict
0x1686502b…a1d2
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x1d4c90ab…1ba7
0xb72e62…7777
4 touches
1 conflict
0x44ad89ba…cf83
0xb72e62…7777
4 touches
1 conflict
0x00000000…0000
0x86dfd5…6a7d
4 touches
1 conflict
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
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:
0x86dfd554…906a7d
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity