pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,465,248
← previous block
next block →
recent activity
Analyzing
Block #74,465,248
14 transactions · 7 stateful · 2026-05-14 04:33:01 UTC
Parallelism
86
/100
Blocked
14
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,465,248
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
updatePrices
#6
updateDataFeedsValuesPartial
#7
execute
#8
relay
#9
setData
#10
0xd90117…7040
#11
0x39435dac
#12
0x39435dac
· blocks 1
#13
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
12
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x5ddc5828…3893
0x3e4f2b…ba84
2 touches
0 conflicts
0x00359dc0…07b7
0x6f92c7…6a92
2 touches
0 conflicts
0x5e04a46b…2710
0x6f92c7…6a92
2 touches
0 conflicts
0x3e970ad7…f223
0x754704…b603
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:
0x34b6552d…112a6f
1 conflict on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity