pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,346,829
← previous block
next block →
recent activity
Analyzing
Block #74,346,829
12 transactions · 10 stateful · 2026-05-13 15:24:49 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,346,829
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x39ecce49
· blocks 1
#3
0x1094dc9f
#4
0x6a049838
#5
updatePrices
#7
0x98717539
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
setData
#11
forward
#6
exec
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce2b6650…ecc3
0x5c2513…7777
4 touches
1 conflict
0x00c46468…f328
0x3bd359…433a
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0xcc67aa…c71c
4 touches
1 conflict
0x00000000…0003
0xcc67aa…c71c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x6aa624fd…a84c
0x1b6862…e19c
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
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:
0x5c2513cf…487777
1 conflict on slot
0xce2b6650f3…b0ecc3
Audit this contract →
← previous block
·
next block →
recent activity